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.

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

Extend field stats to report searchable/aggregatable fields #17980

Merged
merged 1 commit into from
Apr 27, 2016
Merged

Extend field stats to report searchable/aggregatable fields #17980

merged 1 commit into from
Apr 27, 2016

Conversation

jimczi
Copy link
Contributor

@jimczi jimczi commented Apr 26, 2016

  • Add isSearchable and isAggregatable (collapsed to true if any of the instances of that field are searchable or aggregatable).
  • Accept wildcards in field names.
  • Add a section named conflicts for fields with the same name but with incompatible types (instead of throwing an exception).

This closes #17750

final static String MAX_DOC = new String("max_doc");
final static String DOC_COUNT = new String("doc_count");
final static String DENSITY = new String("density");
final static String SUM_DOC_FREQ = new String("sum_doc_freq");
final static String SUM_TOTAL_TERM_FREQ = new String("sum_total_term_freq");
final static String IS_SEARCHABLE = new String("is_searchable");
final static String IS_AGGREGATABLE = new String("is_aggregatable");
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should it be just searchable/aggregatable (without the is_ prefix) as suggested in the original issue?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

on the other hand I would agree to keep isSearchable/isAggregatable in the Java API

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done in 49cd8a4

@jpountz
Copy link
Contributor

jpountz commented Apr 26, 2016

I left some comments but I think this is close!

@jimczi
Copy link
Contributor Author

jimczi commented Apr 27, 2016

Thanks @jpountz I've pushed another commit.

@jpountz
Copy link
Contributor

jpountz commented Apr 27, 2016

I left another comment regarding the visibility of these new isSearchable/isAggregatable methods. Otherwise it looks good to me.

* Add isSearchable and isAggregatable (collapsed to true if any of the instances of that field are searchable or aggregatable).
* Accept wildcards in field names.
* Add a section named conflicts for fields with the same name but with incompatible types (instead of throwing an exception).
@jimczi jimczi merged commit f600c4a into elastic:master Apr 27, 2016
@jimczi jimczi deleted the extend_field_stats branch April 27, 2016 15:18
@jimczi
Copy link
Contributor Author

jimczi commented Apr 27, 2016

Thanks @jpountz
I've change the visibility of the new methods in MappedFieldType.
Merged f600c4a

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Data Management/Stats Statistics tracking and retrieval APIs >feature v5.0.0-alpha3
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Extend field stats to include type, searchable, aggregatable
3 participants