MongoDB: Improve type mapper discriminating between INTEGER and BIGINT #235
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
amotl
requested review from
surister,
matkuliak,
wierdvanderhaar and
hlcianfagna
surister
reviewed
Aug 21, 2024
amotl
force-pushed
the
amo/mongodb-bigint
branch
from
d1c0740 to
ba7b8f3
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
About
@matkuliak reported that the MongoDB I/O subsystem wasn't capable to map values like
Long('1563051934000')to CrateDB SQL'sBIGINTdata type.1563051934000to typeinteger#219This patch improves the situation.