Over a million developers have joined DZone.

MongoDB Driver Issues Are Now Public

DZone's Guide to

MongoDB Driver Issues Are Now Public

· Java Zone ·
Free Resource

Build vs Buy a Data Quality Solution: Which is Best for You? Gain insights on a hybrid approach. Download white paper now!


For the last year, the MongoDB drivers team has focused on standardizing our eleven official drivers. Gradually, we're cleaning up inconsistent behaviors and APIs. Ideally, users and our customer-support team need to learn MongoDB once, instead of re-learning MongoDB in each programming language. We're also sharing our bugfixes among drivers: if I made a mistake, there's a good chance someone else made the same mistake in another language. We publish our bugfixes to the team so everyone can check their code.

We've tracked these cross-language bugs and standards in a private Jira project, "DRIVERS". Last week, that project went public. Anyone can comment, browse tickets, and create new ones.

In the past you could see issues in each driver's project, like the "PYTHON" or "JAVA" projects. Those were always public. But not the umbrella DRIVERS tickets. We felt that we needed a private place to propose and debate features, for a few reasons: We wanted to talk about specific customers' requirements in confidence, and we wanted to discuss controversial features frankly among ourselves, before getting the community's opinion. We worried that if we didn't have a private place to discuss them in Jira, we'd use email and lose the advantages of a ticket-tracking system. The cross-language bugfixes didn't need to be private but they were by default, since they were in the same project as the cross-language features.

But we changed our minds about these private discussions. The MongoDB server's tickets have always been public, after all. Our drivers are open source and we develop in the open, so the DRIVERS project should be open too. We'll still use private comments when we discuss particular customers' needs, of course. But now the default for DRIVERS tickets is open, not closed.

Build vs Buy a Data Quality Solution: Which is Best for You? Maintaining high quality data is essential for operational efficiency, meaningful analytics and good long-term customer relationships. But, when dealing with multiple sources of data, data quality becomes complex, so you need to know when you should build a custom data quality tools effort over canned solutions. Download our whitepaper for more insights into a hybrid approach.


Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}