Open nik9000 opened 2 years ago
Pinging @elastic/es-search (Team:Search)
Pinging @elastic/es-analytics-geo (Team:Analytics)
@nik9000 does synthetic source leverage _source_include
/_source_exclude
for the fields it has to synthesize?
@nik9000 does synthetic source leverage
_source_include
/_source_exclude
for the fields it has to synthesize?
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?
Hello @nik9000 , can I pick some of the unchecked subtasks?
I think all of the unchecked tasks are quick difficult to be honest. ignore_malformed
are maybe easier, but I wouldn't suggest picking it up.
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.
@nik9000 does synthetic source leverage
_source_include
/_source_exclude
for the fields it has to synthesize?It does not. There is no support at the moment for any kind of partial synthesis.
Hi @nik9000 - just for my own clarity. You can either use mode: synthetic on its own or use the _source_include
/_source_exclude
? But the two cannot be combined ? Is this correct ?
Hi @nik9000 - just for my own clarity. You can either use mode: synthetic on its own or use the
_source_include
/_source_exclude
? But the two cannot be combined ? Is this correct ?
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)
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
#87270synthetic: true
tosynthetic: strict
so we have room to add more later. We totally will. @romseygeekLater
aggregate_metric_double
field type #88909constant_keyword
#88603dense_vector
#89840histogram
#89833keyword
fields withignore_above
(#87480 + #89466)match_only_text
#89516version
#89706_doc_count
#91465fields
in runtime fields scriptsip
#89888text
(#89950 + more)keyword
(#89950)match_only_text
(#89950)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
#90007ip
#90038numeric
#90428scaled_float
#109506date
/date_nanos
#109410geo_point
#109651histogram
#109882aggregate_double_metric
#108746 #109888text
type family https://github.com/elastic/elasticsearch/pull/106338keyword
https://github.com/elastic/elasticsearch/pull/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.