[
https://issues.apache.org/jira/browse/SOLR-11031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrzej Bialecki updated SOLR-11031:
-------------------------------------
Attachment: SOLR-11031.patch
This patch adds the functionality to save serialized events and their context
(including execution plan), as well as other related changes:
* {{CollectionAdminParams.SYSTEM_COLL}} is used consistently instead of literal
{{.system}}.
* {{SystemCollectionSchema.xml}} has been modified to accommodate other
document types than blobs. I also added several dynamic fields that provide
some flexibility when storing other event types in the system collection.
* {{LogPlanAction}} tries to strike a balance between the level of details and
the number of fields in the index - some key details are extracted into
separate fields to facilitate easy searching and presentation, but the
remaining parts of event and context properties are stored as non-indexed JSON
strings. The upside of this is that it's possible to evolve this schema using
the stored blobs.
* unit test.
> Implement LogPlanAction for autoscaling
> ---------------------------------------
>
> Key: SOLR-11031
> URL: https://issues.apache.org/jira/browse/SOLR-11031
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Components: AutoScaling, SolrCloud
> Reporter: Shalin Shekhar Mangar
> Assignee: Andrzej Bialecki
> Labels: autoscaling
> Fix For: master (8.0), 7.1
>
> Attachments: SOLR-11031.patch
>
>
> The LogPlanAction should be used to persist events, computed plans and
> execution results to the .system collection by default. We can use this
> information later for analysis as well as to surface hints & history in the
> Admin UI.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
