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

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

Github user justinleet commented on the issue:

    https://github.com/apache/metron/pull/1065
  
    Do you think it's worthwhile to add something at the beginning like:
    
    > Metron version = x
    > ES version = y
    
    At least then we'd be letting people know what version things were tested 
on, as well as at least giving them a path to looking at things like the 
upgrading.md, learning about schema changes, etc. to adapting an older use case.


> Fixes for forensic clustering use case example
> ----------------------------------------------
>
>                 Key: METRON-1620
>                 URL: https://issues.apache.org/jira/browse/METRON-1620
>             Project: Metron
>          Issue Type: Bug
>            Reporter: Michael Miklavcic
>            Assignee: Michael Miklavcic
>            Priority: Major
>
> ES mapping needed some adjustments. Change to dynamic template mapping so it 
> will work for non-existent indexes yet to be created. Make work with ES 5.6.x 
> data types.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to