-
Notifications
You must be signed in to change notification settings - Fork 25k
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
Should we remove/modify some of the experiment tags in the documentation #19798
Comments
Interestingly if I had built the same table, I would probably have the opposite action in most cases. :) For instance I think the derivative pipeline aggs or the profile flag map to common use-cases (even though in the case of the profile agg we would probably still need a note that the response format may change). I'd probably also wait for pipeline aggs to be exposed in Kibana since that would be a very good test of the usability of pipeline aggs, but this is something I hope we'll be able to do soon. On the other hand, I don't like exposing options about internals like the terms agg execution hint or percentiles implementation. In the case of percentiles, I am wondering whether we could replace the option with something that characterizes the data or the expected accuracy without being implementation specific and would allow us to pick an impl internally. |
Discussed in Fix It Friday and have updated the table to reflect what we talked about |
@colings86 what is left to do here? anything to discuss further? |
Nothing to discuss further but the items above that have "remove tag" in the action need to have the experimental tag removed |
@colings86 we should consider which features should use the beta tag instead (ie we will support this feature and plan to keep it, but the API may change significantly) |
Relates #19798 Removed experimental label from: * Painless * Diversified Sampler Agg * Sampler Agg * Significant Terms Agg * Terms Agg document count error and execution_hint * Cardinality Agg precision_threshold * Percentile Agg compression and HDR Histogram * Percentile Rank Agg HDR Histogram * Pipeline Aggregations * index.shard.check_on_startup * index.store.type (added warning) * Preloading data into the file system cache * foreach ingest processor * Field caps API * Profile API Added experimental label to: * Moving Average Agg Prediction Changed experimental to beta for: * Adjacency matrix agg * Normalizers * Tasks API * Index sorting Labelled experimental in Lucene: * ICU plugin custom rules file * Flatten graph token filter * Synonym graph token filter * Word delimiter graph token filter * Simple pattern tokenizer * Simple pattern split tokenizer * Analysis explain output format * Segments verbose output format
Relates #19798 Removed experimental label from: * Painless * Diversified Sampler Agg * Sampler Agg * Significant Terms Agg * Terms Agg document count error and execution_hint * Cardinality Agg precision_threshold * Pipeline Aggregations * index.shard.check_on_startup * index.store.type (added warning) * Preloading data into the file system cache * foreach ingest processor * Field caps API * Profile API Added experimental label to: * Moving Average Agg Prediction Changed experimental to beta for: * Adjacency matrix agg * Normalizers * Tasks API * Index sorting Labelled experimental in Lucene: * ICU plugin custom rules file * Flatten graph token filter * Synonym graph token filter * Word delimiter graph token filter * Simple pattern tokenizer * Simple pattern split tokenizer Replaced experimental label with warning that details may change in the future: * Analysis explain output format * Segments verbose output format * Percentile Agg compression and HDR Histogram * Percentile Rank Agg HDR Histogram
Updated the table in the description to account for removed tags in #25727 |
Pinging @elastic/es-search-aggs |
Closing this as its no longer relevant |
Below is a list of the experimental tags that are in the documentation at the time of writing (I've used blame view for the links only so I can skip to the experimental tag in the file). I have added the link to the PR that added the tag and the version it was added in (where I can find it) to each in the list as well as what I think we should do with the tag (remove or keep):
predict
paramindex.store.type
fixed_auto_queue_size
The text was updated successfully, but these errors were encountered: