The Altair Community is migrating to a new platform to provide a better experience for you. In preparation for the migration, the Altair Community is on read-only mode from October 28 - November 6, 2024. Technical support via cases will continue to work as is. For any urgent requests from Students/Faculty members, please submit the form linked here

bug report :NumberInt not supported in execute Mongo command

kaymankayman Member Posts: 662 Unicorn
edited December 2018 in Product Feedback - Resolved

When using the Mongo command for bulk operations it seems NumberInt is not accepted. There is a BSON error given, while the same command works fine when using the mongo shell directly. Converting the NumberInt to NumberLong does work fine, but it is a bit inconvenient because all integers will be store as 64 instead of 32bit values, having a negative impact on size. Ommiting the Number is also not a valid option since it will be stored as real.

This works :

 

{update: "test_db", updates: [ { q: {"_id":NumberLong(123456)}, u: {"just something":"some value"},upsert:true}], ordered: false, writeConcern: { w: 0, wtimeout: 0 }}

 

This doesn't :

 

{update: "test_db", updates: [ { q: {"_id":NumberInt(654321)}, u: {"just something":"some value"},upsert:true}], ordered: false, writeConcern: { w: 0, wtimeout: 0 }}

 

  • Message: JSON reader was expecting a value but found 'NumberInt'.

 

Thanks for checking !

Tagged:
0
0 votes

Declined · Last Updated

No activity or votes since Sep 2017. Please comment and cc sgenzer if this should be reopened. NOSQL-47

Comments

  • sgenzersgenzer Administrator, Moderator, Employee-RapidMiner, RapidMiner Certified Analyst, Community Manager, Member, University Professor, PM Moderator Posts: 2,959 Community Manager
  • sgenzersgenzer Administrator, Moderator, Employee-RapidMiner, RapidMiner Certified Analyst, Community Manager, Member, University Professor, PM Moderator Posts: 2,959 Community Manager

    pushed to dev team.

     

    SG

     

Sign In or Register to comment.