[ 
https://issues.apache.org/jira/browse/METRON-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16498397#comment-16498397
 ] 

ASF GitHub Bot commented on METRON-1547:
----------------------------------------

Github user justinleet commented on the issue:

    https://github.com/apache/metron/pull/1037
  
    I haven't been able to reproduce Solr not making the delete call, and given 
that the code is the same between ES and Solr, I'm inclined to call it a 
browser issue.
    
    I have spun this back up for both ES and Solr (with the caveat that the 
default "source.type.field" for ES is broken until master is merged all the way 
down.
    
    At this point both work, after a minor fix that would result in an off by 
one error in the UI when deleting.  The UI is functional for both, although 
with the previously mentioned preexisting latency issue in updating, I do 
recommend closing and reopening the tab or things don't line up correctly.
    
    At this point, the only issue is the indexString.


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

Reply via email to