[jira] [Created] (METRON-1312) Make implementation of findOne consistent between ES and HBase

["Justin Leet (JIRA)" <ji...@apache.org>]

Justin Leet created METRON-1312:
-----------------------------------

             Summary: Make implementation of findOne consistent between ES and HBase
                 Key: METRON-1312
                 URL: https://issues.apache.org/jira/browse/METRON-1312
             Project: Metron
          Issue Type: Bug
            Reporter: Justin Leet


Right now, the implementations differ slightly because of sensorType parameter.

Elasticsearch will take the parameter and use it to determine a type for the ids query it runs.  This means that the GUID will be found only if it's in the provided sensor (and will return nothing if it's present in another sensor).

HBase completely ignores sensorType and returns it no matter what sensor type.

Given that the GUIDs are universal, we can probably just chop out sensorType completely from the API call.  This probably primarily impacts the UI, but if anyone is using this endpoint outside of this, it would be a breaking change.

We could also just make the change to the underlying call to ignore the parameter completely.  I don't think any discussion around API deprecation and versioning has occurred, so this might be safer.



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