Skip to content

Mapper: Allow to define CamelCase JSON fields in mapping definitions #133

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
Closed
kimchy opened this issue Apr 14, 2010 · 1 comment
Closed

Mapper: Allow to define CamelCase JSON fields in mapping definitions #133

kimchy opened this issue Apr 14, 2010 · 1 comment
Labels
>enhancement v0.07.0

Comments

@kimchy
Copy link
Member

kimchy commented Apr 14, 2010

They will be converted to underscore case fields
@kimchy
Copy link
Member Author

kimchy commented Apr 14, 2010

Mapper: Allow to define CamelCase JSON fields in mapping definitions, closed by 2d6de97.

tlrx added a commit that referenced this issue Jun 5, 2015
@tlrx
Fix constructors of ZenDiscovery's sub classes
338a94d 
Closes #133
@makeyang makeyang mentioned this issue Sep 7, 2015
Closed
cbuescher pushed a commit to cbuescher/elasticsearch that referenced this issue Oct 2, 2023
@danielmitterdorfer
Apply setup user-tag logic consistently
2ca3f26 
With this commit we always take all parameters into account when
determining the `setup` user-tag. Previously, we have always used "bare"
as value regardless of the specific setup. This means that the query
that attempts to deactivate outdated results will never match any
document (because they are copied to the release environment with the
proper setup tag). Queries that rely on this logic may produce invalid
results as a consequence.

Relates elastic#133
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
>enhancement v0.07.0
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kimchy