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

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

GitHub user nickwallen opened a pull request:

    https://github.com/apache/metron/pull/793

    METRON-1226 Searching Can Errantly Query the Wrong Indices

    The ElasticsearchDAO can errantly query the wrong indices under certain 
conditions. This can occur when there are at least two different sensors that 
have been configured with a similar name prefix.
    
    For example, consider the case when the user has created two different 
sensors; "snort" and "snort_v2".  When the user attempts to query the "snort" 
index in Elasticsearch, the query generated by the ElasticsearchDAO will hit 
both of these indices which is unexpected.
    
    ## Pull Request Checklist
    
    - [ ] Is there a JIRA ticket associated with this PR? If not one needs to 
be created at [Metron 
Jira](https://issues.apache.org/jira/browse/METRON/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel).
 
    - [ ] Does your PR title start with METRON-XXXX where XXXX is the JIRA 
number you are trying to resolve? Pay particular attention to the hyphen "-" 
character.
    - [ ] Has your PR been rebased against the latest commit within the target 
branch (typically master)?
    - [ ] Have you included steps to reproduce the behavior or problem that is 
being changed or addressed?
    - [ ] Have you included steps or a guide to how the change may be verified 
and tested manually?
    - [ ] Have you ensured that the full suite of tests and checks have been 
executed in the root metron folder via:
    - [ ] Have you written or updated unit tests and or integration tests to 
verify your changes?
    - [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)? 
    - [ ] Have you verified the basic functionality of the build by building 
and running locally with Vagrant full-dev environment or the equivalent?
    
    


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/nickwallen/metron METRON-1226

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/metron/pull/793.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #793
    
----
commit 4ab87f55d30b584c7943edfb8bfc5cbca89eabde
Author: Nick Allen <n...@nickallen.org>
Date:   2017-10-03T22:10:00Z

    METRON-1226 Searching Can Errantly Query the Wrong Indices

----


> Searching Can Errantly Query the Wrong Indices
> ----------------------------------------------
>
>                 Key: METRON-1226
>                 URL: https://issues.apache.org/jira/browse/METRON-1226
>             Project: Metron
>          Issue Type: Bug
>            Reporter: Nick Allen
>            Assignee: Nick Allen
>
> The ElasticsearchDAO can errantly query the wrong indices under certain 
> conditions.  This can occur when there are at least two different sensors 
> that have been configured with a similar name prefix.
> For example, if you have have configured both a "snort" and "snort_v2" 
> sensor, the query generated by the ElasticsearchDAO will hit both of those 
> indices, when in fact only one or the other is desired.



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

Reply via email to