[
https://issues.apache.org/jira/browse/METRON-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16501974#comment-16501974
]
ASF GitHub Bot commented on METRON-1547:
----------------------------------------
Github user justinleet commented on the issue:
https://github.com/apache/metron/pull/1037
Index removed from rest calls. I spun up full dev and confirmed both ES and
Solr still work as expected, and that the calls do not pass along index
anymore. Feature branch merged in to resolve conflicts.
> Solr Comment Fields
> -------------------
>
> Key: METRON-1547
> URL: https://issues.apache.org/jira/browse/METRON-1547
> Project: Metron
> Issue Type: Sub-task
> Reporter: Justin Leet
> Assignee: Justin Leet
> Priority: Major
>
> Right now the Solr schemas don't have comment fields defined. It'll get
> caught by the catch all with ignored type not multivalued.
> ES just handles this correctly out of the box, but we'll need to take care of
> it in Solr and document the schema restriction.
> This actually is probably fairly problematic in comparison to ES. Solr
> doesn't support an easy way of doing a complex structure without doing
> something a bit weird (like parsing a string representation) or miserable
> (nested document).
> This will be incompatible with the current comment update system (just using
> the patch() functionality). Preferably we need to add a new REST endpoint for
> comments specifically so that we can handle it without the frontend knowing
> the backend system. This also involves adjusting the UI to use the new REST
> API, along with testing for both ES and Solr.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
