You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@metron.apache.org by "Justin Leet (JIRA)" <ji...@apache.org> on 2018/05/03 16:04:00 UTC

[jira] [Updated] (METRON-1547) Solr Comment Fields

     [ https://issues.apache.org/jira/browse/METRON-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Justin Leet updated METRON-1547:
--------------------------------
    Issue Type: Sub-task  (was: Bug)
        Parent: METRON-1416

> 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)