[CSHARP-1278] Connect calls buildInfo in 1.x branch Created: 13/May/15 Updated: 05/Apr/19 Resolved: 09/Dec/15 |
|
| Status: | Closed |
| Project: | C# Driver |
| Component/s: | None |
| Affects Version/s: | 1.10, 2.0 |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jonathan Reams | Assignee: | Robert Stam |
| Resolution: | Done | Votes: | 0 |
| Labels: | question | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Description |
|
We changed what gets reported in buildInfo, and now connect fails in the 1.x branch of the C# driver. Connect calls both ping and buildInfo before returning, and the buildInfo call seems to capture only a small part of the information available even before the recent changes. Can connect not call buildInfo? The info in buildInfo is mostly useful internally during testing to exclude certain tests from certain OSs/architectures and for debugging. Although it's available to users and documented, it's not something most users should have to use very often - let alone be valuable enough to fetch/parse on every connect. Also, can constructing the buildInfo class not fail if some fields are missing? I think there may be further changes to buildinfo in master/3.2 as we refactor the build system. |
| Comments |
| Comment by Robert Stam [ 09/Dec/15 ] |
|
The C# driver (and possibly others) were using the "bits" field in the buildInfo result returned from the server. The server team removed the "bits" field from the buildInfo result, but once they learned that some drivers were depending on it they decided to leave it in. |
| Comment by Bernie Hackett [ 13/May/15 ] |
|
jonathan.reams@10gen.com, is there a SERVER ticket related to these changes? If not, the tickets that these changes are related to need to have "Driver Changes" set to "Needed". |
| Comment by Bernie Hackett [ 13/May/15 ] |
|
I can see this server change breaking a bunch of drivers (both tests and public API) and third party tools. Luckily, PyMongo's server_info method just returns the raw result from calling buildinfo, and isn't called internally. |