docs: Add Elasticsearch unsigned_long → UInt64 type mapping#1742
Merged
Conversation
The Elasticsearch connector now decodes `unsigned_long` to Arrow `UInt64` to cover the full u64 range without overflowing through i64. Add the mapping to the Elasticsearch type table. Source: spiceai/spiceai#10825
✅ Pull with Spice PassedPassing checks:
|
1 similar comment
✅ Pull with Spice PassedPassing checks:
|
|
🚀 deployed to https://00e334dd.spiceai-org-website.pages.dev |
|
🚀 deployed to https://4b8252bc.spiceai-org-website.pages.dev |
lukekim
approved these changes
May 18, 2026
This file contains hidden or 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
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.
Summary
Add the
unsigned_longrow to the Elasticsearch type-mapping table now that the connector decodes it explicitly to ArrowUInt64.Source PRs
Changes
website/docs/components/data-connectors/elasticsearch/index.mdunsigned_long → UInt64to the type-mapping table, with a note that the decoder accepts both numeric values and digit-string representations (since JS clients commonly serialize values > 2^53-1 as strings).Test plan
cd website && npm run buildpasses locallySome("unsigned_long") => DataType::UInt64)