[jira] [Created] (SAMZA-654) Add Elasticsearch Producer

["Dan Harvey (JIRA)" <ji...@apache.org>]

Dan Harvey created SAMZA-654:
--------------------------------

             Summary: Add Elasticsearch Producer
                 Key: SAMZA-654
                 URL: https://issues.apache.org/jira/browse/SAMZA-654
             Project: Samza
          Issue Type: New Feature
            Reporter: Dan Harvey
            Assignee: Dan Harvey
            Priority: Minor


Elasticsearch is likely to be a common output datastore for Samza so it would be good to have a Producer (and possibly Consumer) as part of the core project.


Elasticsearch organises data into indexes which can contain multiple types of documents. Each document has a id which it is identified by and the source which is it's actual data. These map well on to concepts in Samza. 


Elasticsearch also has mappings which defines how it indexes the documents pushed to it. I don't think the Samza System should be concerned with this. 


(index, type) -> stream

id -> key

source -> message

The main one needing to be agreed upon is how the index and type are defined. We've started by simply joining them with a / as they would in the elasticsearch REST api.

The java elasticsearch client can deal with the source being a variety of types that can be presented as json. We could just pass objects to the Producer or use the Samza json serde to handle that (or maybe both).

Elasticsearch also has the ability to bulk index documents, so combining this with correctly flushing the Producer can get good performance.

Finally we'd need to think how this can be configured. Elasticsearch java client has two different transports that have various configuration. Currently we are only using the TransportClient, we should probably make it configurable or maybe not initially.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)