37cd03ad4d
In c++ the results are built all together under a bucket hierarchy. This buckets was written out and java would read it and split the bucket into its parts: the bucket itself, its records and its influencers. During the migration, the bucket started being persisted as a whole, including its records and influencers. This commit is changing this by modifying the way results are written in c++. This way, the java and c++ results writing/reading are in sync. To achieve this, the change involved writing records and influencers as top level results from c++. In addition, they are written as an array object in order to allow the java side to persist them in a bulk request. * Fix bucket counting in results processor Original commit: elastic/x-pack-elasticsearch@feadf3f887 |
||
|---|---|---|
| elasticsearch | ||
| vagrant | ||
| LICENSE.txt | ||
| build.gradle | ||
| gradle.properties | ||
| settings.gradle | ||