[
https://issues.apache.org/jira/browse/METRON-1448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16356073#comment-16356073
]
ASF GitHub Bot commented on METRON-1448:
----------------------------------------
Github user cestella commented on the issue:
https://github.com/apache/metron/pull/929
What do you mean "auto-commit"? By default it will commit at the batch
level as the other writers do. You can turn that behavior off and it'll commit
when the Solr client decides at the cost of possibly losing data.
Regarding solr vs solrcloud, to my understanding solr is the product and
solrcloud is a way of running Solr. The other way is solr standalone.
Originally we named things after the product, which I think is correct, and
have made explicit that we support Solr running in Solr Cloud mode in the docs.
> Update SolrWriter to conform to new collection strategy
> -------------------------------------------------------
>
> Key: METRON-1448
> URL: https://issues.apache.org/jira/browse/METRON-1448
> Project: Metron
> Issue Type: Improvement
> Reporter: Casey Stella
> Priority: Major
>
> Currently the SolrWriter presumes a single collection to be written to. The
> new collection strategy for Solr implies a collection per sensor. Also,
> there are a few rough edges in the writer which could stand smoothing:
> * By default, we use solr's implicit commit mechanism, rather than
> committing at the batch granularity. This may result in lost data on worker
> failure.
> * We do not use the the batch add api, but rather message-by-message add
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
