[
https://issues.apache.org/jira/browse/CAMEL-12738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16638271#comment-16638271
]
Dmitry Volodin commented on CAMEL-12738:
----------------------------------------
[~tim.sexton], could you please confirm your assumption. You can look at the
JUnit tests and see that operations could use exchange headers and support for
dynamic parameters:
{code:java}
headers.put(ElasticsearchConstants.PARAM_OPERATION,
ElasticsearchOperation.Index);
headers.put(ElasticsearchConstants.PARAM_INDEX_NAME, "twitter");
headers.put(ElasticsearchConstants.PARAM_INDEX_TYPE, "tweet");
headers.put(ElasticsearchConstants.PARAM_INDEX_ID, "1");
{code}
Which operation doesn't support headers for indexName and intexType?
> Update Elasticsearch-Rest Component to allow index name and type to be set at
> runtime
> -------------------------------------------------------------------------------------
>
> Key: CAMEL-12738
> URL: https://issues.apache.org/jira/browse/CAMEL-12738
> Project: Camel
> Issue Type: Improvement
> Components: camel-elasticsearch-rest
> Reporter: Tim Sexton
> Priority: Minor
>
> Right now the Elasticsearch component must be defined with a static index
> name and index type, these must be hardcoded into the endpoint. This means
> for every possible index that might be searched a brand new route must be
> created (lots of simple inheritance).
>
> This would be easier if the index name and type could be defined at runtime
> in the same way a query is defined.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
