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 fields #11650

Closed

dopesong opened this issue Jun 14, 2015 · 1 comment

dopesong commented Jun 14, 2015

I found this explanation about my issue:

http://elasticsearch-users.115913.n3.nabble.com/Number-Format-Exception-td1474946.html

Ahh, yes, this is a limitation in elasticsearch. Basically, all types are broken down into Lucene Documents, with their "typeness" added by elasticsearch. The limit to that is the fact that a field with the same name across different types within the same index must be of the same type (long/integer/string). The problem does not exists between indices.

So is this going to change? Because why one type field is realted to another?

Contributor

clintongormley commented Jun 14, 2015

No it isn't going to change. In fact we're getting stricter about enforcing this restriction. See #8870

A blog post will be coming soon to explain the problems, and the changes we've made to resolve them.

clintongormley closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment