[CSHARP-1991] Add support for OP_COMPRESSED Created: 01/Jun/17  Updated: 28/Oct/23  Resolved: 03/Jun/19

Status: Closed
Project: C# Driver
Component/s: Wire Protocol
Affects Version/s: None
Fix Version/s: 2.9.0

Type: New Feature Priority: Major - P3
Reporter: Rathi Gnanasekaran Assignee: Dmitry Lukyanov (Inactive)
Resolution: Fixed Votes: 8
Labels: driver-current-quarter
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by DRIVERS-381 Add support for reading and writing O... Closed
Epic Link: .NET MongoDB 3.6 support

 Comments   
Comment by Githook User [ 02/Jun/19 ]

Author:

{'name': 'Dmitry Lukyanov', 'email': 'dmitry.lukyanov@mongodb.com', 'username': 'DmitryLukyanov'}

Message: CSHARP-1991: Add zlib and snappy compressions.
Branch: master
https://github.com/mongodb/mongo-csharp-driver/commit/1c5493fa4c9593abaf15a2d8464a762baa35045a

Comment by Githook User [ 02/Jun/19 ]

Author:

{'name': 'Alexander Endris', 'email': 'qudeid@alexendris.com', 'username': 'AlexEndris'}

Message: CSHARP-1991: Add support for OP_COMPRESSED.
Branch: master
https://github.com/mongodb/mongo-csharp-driver/commit/d701854de8deea6d24fcc8478f3687d7c4251d91

Comment by Bernie Hackett [ 14/Feb/19 ]

sherry-ummen, 2020Q1 is this quarter. For our internal planning metadata we use MongoDB's fiscal year, which started February 1. We're in fiscal year 2020 right now. Sorry for the confusion.

Comment by Sherry Ummen [ 14/Feb/19 ]

And it has been moved again now to 2020Q1. God help us. Seems like C# driver is getting very less attention compared to other drivers. Wonder whether C# driver will be abandoned by Mongodb? I really waiting for this feature ofcourse an official version.

Comment by Ian Whalen (Inactive) [ 12/Dec/18 ]

Hi Qudeid et al.,

My apologies for the delay in responding to you all here! Going forward we're really putting a focus on providing feedback for tickets and PRs; even if we don't have the time to immediately merge them we're aiming to provide a quick response so you know roughly where each issue stands. This will take some time as the team starts to work through the backlog, but those of you with tickets and PRs should start to see activity as we work through the full queue.

Please be assured that we are not "freezing features" and the team is hard at work with bug fixes, new features, and ensuring compatibility with all of the latest MongoDB Server features. You can see here the 80+ bug fixes/improvements the team delivered in the past year.

So once again: my apologies for allowing these conversation to slip through the cracks in the past, but please know that we are re-dedicating ourselves to engaging the community in a timely fashion. Thank you for your patience while we tackle your reports, requests and PRs.

(Also, in re this ticket, there's a unique MongoDB-ism that's likely causing additional confusion: our fiscal year starts and ends on February 1, so the labeling of "FY2019Q4 Best Case" actually means we were aiming to work on this by January 31, 2019 (best case depending on other bugs that arise and take the team's time). It's weird, I know - my apologies for that.)

Comment by Alex Endris [ 06/Nov/18 ]

I'm sorry, but "FY2019 best case" is beyond ridiculous. You got the help from your community, have the solution already production tested for months! No comment on that pull request, no nothing.

How can something that's already implemented, but nobody cares to take a look, be pushed back so far??? Also... 0 communication to comments here.

I really expect an explanation!

Comment by Ivan Artemov [ 05/Nov/18 ]

What happened with development process? Why all features freezed?

Comment by Narayana Rengaswamy [ 25/Sep/18 ]

It would be great to get an ETA on this.. Thanks!

Comment by Alex Endris [ 13/Jul/18 ]

Hi again,

just wanted to say, as a side note, that we're running on that version of my pull request for about a month now and it has worked flawlessly. I'm still eagerly awaiting feedback.

Thank you.

 

Comment by Alex Endris [ 14/Jun/18 ]

Hi, since we were in dire need of compression, I took it into my hands to provide an implementation of the specification inspired by the mongo-java-driver implementation. See here: https://github.com/mongodb/mongo-csharp-driver/pull/328

Please provide feedback.

Comment by Alex Endris [ 28/May/18 ]

As the beta for version 2.7 is already out and I can't see anything on github relating to compression, will this really make it into 2.7? Traffic compression would help us tremendously.

Comment by Bernd Schäfer [ 02/May/18 ]

Hi,

any update on when this feature will be available?

Thanks,

Bernd

Comment by Ken Cottrell [ 10/Jan/18 ]

Thanks. I was really hoping there would be a roadmap with an expected schedule, but that's good to know.

Comment by Robert Stam [ 10/Jan/18 ]

We use JIRA to manage what features will go into a particular version (so in a sense JIRA is the roadmap).

You can monitor the ongoing changes to the features expected in 2.6 in JIRA with this JIRA filter:

https://jira.mongodb.org/issues/?jql=project%20%3D%20CSHARP%20AND%20fixVersion%20%3D%202.6%20ORDER%20BY%20key%20ASC

We don't have a release date for 2.6 yet, but I except it will be within the next month or two.

Comment by Ken Cottrell [ 10/Jan/18 ]

Thanks, Robert. Is there somewhere that details the expected roadmap for the C# driver, or is there an anticipated date that driver version 2.6 will drop? I'm looking forward to this change being implemented.

Comment by Robert Stam [ 10/Jan/18 ]

Ignore the label on the epic. Fiscal quarters have names that are hard to make sense of.

This work is scheduled for version 2.6 of the driver which is the next version of the driver.

Comment by Ahmed Makhdoom [ 27/Dec/17 ]

Is there an ETA for this? The Epic seems to say Q4 2018 - is that really the case?

We're considering implementing it ourselves if it'll really take that long.

Generated at Wed Feb 07 21:41:18 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.