<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Wed Feb 07 21:09:50 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>MongoDB Jira</title>
    <link>https://jira.mongodb.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>9.7.1</version>
        <build-number>970001</build-number>
        <build-date>13-04-2023</build-date>
    </build-info>


<item>
            <title>[CDRIVER-545] libbson does not handle large arrays well</title>
                <link>https://jira.mongodb.org/browse/CDRIVER-545</link>
                <project id="10030" key="CDRIVER">C Driver</project>
                    <description>&lt;p&gt;I have an array in Mongo with a large number of values (e.g. I&apos;m storing some json WebGL models where there are an array of vertices, very big and due to the specification no changes aloud there).&lt;br/&gt;
The mongo driver works well with uploading but when downloading via libbson my arrays get truncated.&lt;br/&gt;
E.g. I have a document with an array of size 1250 amongst other significant stuff. When I run through it with a bson_iter I only count 1185 elements.&lt;br/&gt;
The problem is much much worse when I try to run bson_to_json as the array gets truncated down to ~214 and whats worse there is a trailing comma at the end of the list (I think it collapsed an empty element due to the first truncation) and it won&apos;t parse.&lt;br/&gt;
I am well well under the size limit of the document (4kb BSON) and expect to be able to deal with arrays of size O(100,000).&lt;/p&gt;</description>
                <environment>Both Ubuntu &amp;amp; Amazon Linux</environment>
        <key id="186347">CDRIVER-545</key>
            <summary>libbson does not handle large arrays well</summary>
                <type id="1" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14703&amp;avatarType=issuetype">Bug</type>
                                            <priority id="2" iconUrl="https://jira.mongodb.org/images/icons/priorities/critical.svg">Critical - P2</priority>
                        <status id="6" iconUrl="https://jira.mongodb.org/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="9">Done</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="pchilds">Paul Childs</reporter>
                        <labels>
                            <label>driver</label>
                    </labels>
                <created>Thu, 26 Feb 2015 11:46:27 +0000</created>
                <updated>Wed, 3 May 2017 22:14:23 +0000</updated>
                            <resolved>Thu, 21 May 2015 15:00:37 +0000</resolved>
                                    <version> 1.0.2 </version>
                                                                        <votes>0</votes>
                                    <watches>4</watches>
                                                                                                                <comments>
                            <comment id="838110" author="jason.carey" created="Thu, 26 Feb 2015 17:15:26 +0000"  >&lt;p&gt;That absolutely shouldn&apos;t be happening.&lt;/p&gt;

&lt;p&gt;Can you provide a little more information on how exactly you&apos;re using libmongoc and libbson to pull bson over the network?  I suspect that what you&apos;re actually seeing is corruption, rather than libbson being broken with arrays.  You can check that out by:&lt;/p&gt;

&lt;ul&gt;
	&lt;li&gt;calling bson_validate() on the bson document that appears to have truncated arrays.  If that returns false, you&apos;ll know you&apos;ve got corruption.&lt;/li&gt;
	&lt;li&gt;writing the bson bytes to a file and attaching it to this ticket.  You can access the raw bytes with bson_get_data() and the length with bson-&amp;gt;len.  Once I can see what you&apos;re actually working with I can make a fix if one&apos;s needed.&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Regards,&lt;br/&gt;
Jason&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                                                        <customfield id="customfield_10011" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>Backwards Compatibility</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10038"><![CDATA[Fully Compatible]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_15850" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|hrf7hj:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10558" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1134</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            </customfields>
    </item>
</channel>
</rss>