-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
Synthetic Source #86603
Comments
Pinging @elastic/es-search (Team:Search) |
Pinging @elastic/es-analytics-geo (Team:Analytics) |
@nik9000 does synthetic source leverage |
It does not. There is no support at the moment for any kind of partial synthesis. |
Awesome feature, can't wait to have this in GA!! |
Hello @nik9000 , can I pick some of the unchecked subtasks? |
I think all of the unchecked tasks are quick difficult to be honest. Also you'd need a committer buddy and I've had to move on to other tasks sadly. That might be quite difficult to find too. |
Hi @nik9000 - just for my own clarity. You can either use mode: synthetic on its own or use the |
Right. I honestly didn't know how to combine them so I just declared combining them to be incompatible. Keep in mind synthetic source is only GA for time series indices and data streams. I've had to move on to other things but expect folks will get back to working on getting synthetic source good in more contexts at some point soon. |
Pinging @elastic/es-storage-engine (Team:StorageEngine) |
I'm closing this issue, because most of the mentioned items have been completed. Most of the uncompleted items have dedicated issues. |
This shrinks the index by implementing a "synthetic" _source field. Instead of saving the field to disk we reconstruct it on the fly using our column store, doc values.
Before removing the feature flag
synthetic: true
then we'll have to fail mappings that containenabled: false, synthetic: true
Synthetic source: don't allow disabling source #87270synthetic: true
tosynthetic: strict
so we have room to add more later. We totally will. @romseygeekLater
aggregate_metric_double
field type Addsynthetic_source
support toaggregate_metric_double
fields #88909constant_keyword
Enable synthetic source support on constant keyword fields #88603dense_vector
Synthetic _source: support dense_vector #89840histogram
Synthetic _source: support histogram field #89833keyword
fields withignore_above
(Synthetic source: load text from stored fields #87480 + Synthetic _source: support ignore_above #89466)match_only_text
Synthetic _source: support match_only_text #89516version
Synthetic _source: support version field type #89706_doc_count
Support synthetic _source for _doc_count field #91465fields
in runtime fields scriptsip
REST tests fetching fields with synthetic _source #89888text
(Synthetic _source: supportfield
in many cases #89950 + more)keyword
(Synthetic _source: supportfield
in many cases #89950)match_only_text
(Synthetic _source: supportfield
in many cases #89950)enrich
processor (More tests for enrich processor #89554)fields
API aware of synthetic-ness and go to doc values rather than rebuilding_source
if_source
isn't separately needed.ignore_malformed
Synthetic _source: support ignore_malformed #90007ip
Synthetic_source
:ignore_malformed
forip
#90038numeric
Support malformed numbers in synthetic _source #90428scaled_float
Support synthetic source for scaled_float and unsigned_long when ignore_malformed is used #109506date
/date_nanos
Support synthetic source for date fields when ignore_malformed is used #109410geo_point
Support synthetic source for geo_point when ignore_malformed is used #109651histogram
Support synthetic source together with ignore_malformed in histogram fields #109882aggregate_double_metric
Support synthetic source for aggregate_metric_double when ignore_malformed is used #108746 Simplify ignore_malformed handling for synthetic souce in aggregate_metric_double #109888text
type family Text fields are stored by default in TSDB indices #106338keyword
Synthetic _source: support ignore_above #89466Much later
_recovery_source
- we find that it'd improve write performance by ~11%. We'd have to synthesize on load instead. That's pretty slow. We'd love the 11% but we have to be careful here.The text was updated successfully, but these errors were encountered: