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

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

Github user justinleet commented on a diff in the pull request:

    https://github.com/apache/metron/pull/666#discussion_r131162722
  
    --- Diff: 
metron-platform/metron-elasticsearch/src/test/java/org/apache/metron/elasticsearch/integration/components/ElasticSearchComponent.java
 ---
    @@ -90,6 +95,38 @@ private void cleanDir(File dir) throws IOException {
             }
             dir.mkdirs();
         }
    +
    +    public BulkResponse add(String indexName, String sensorType, String... 
docs) throws IOException {
    +        List<String> d = new ArrayList<>();
    +        for(String doc : docs) {
    --- End diff --
    
    Can be `Collections.addAll(d, docs);`


> Enable the ability to update indexed messages
> ---------------------------------------------
>
>                 Key: METRON-1051
>                 URL: https://issues.apache.org/jira/browse/METRON-1051
>             Project: Metron
>          Issue Type: Improvement
>            Reporter: Casey Stella
>
> Currently our indexing layer is immutable.  It would be useful to be able to:
> * Update data in the indices
> * Track lineage for updates
> Current version of data should be able to be exposed via a batch interface. 
> Updates should be available via a Java DAO API as well as via the REST API.
> Implementation should ensure that the ability to read the current data in 
> batch is possible. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to