Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

number type erasure fix #65

Closed
costin opened this issue Aug 6, 2013 · 1 comment
Closed

number type erasure fix #65

costin opened this issue Aug 6, 2013 · 1 comment
Labels
bug :Hive v1.3.0.M1 wontfix

Comments

@costin
Copy link
Member

costin commented Aug 6, 2013

When adding data, type information such as int or float, get recognized by Elasticsearch to long or double (as there's no mapping in place, the numbers get allocated their maximum space).
This causes problem during deserialization, especially for Hive, which doesn't know how to cast a long to int (or float to double).
costin added a commit that referenced this issue Aug 6, 2013
@costin
add test exposing issue #65
077b0ef
@costin
Copy link
Member Author

costin commented Aug 16, 2013

Since creating a schema for the data upfront was unreliable for complex structures (like map), this has been documented in master.

@costin costin closed this as completed Aug 16, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug :Hive v1.3.0.M1 wontfix
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@costin