[
https://issues.apache.org/jira/browse/SOLR-1431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13050613#comment-13050613
]
Jason Rutherglen commented on SOLR-1431:
----------------------------------------
@Noble I agree, I don't think committing this patch should hold things up.
That was just a little note.
I've been looking at implementing Solr into HBase and am worried [somewhat]
about the ZK libaries. HBase + Solr can help with massive scale near realtime
systems you've described, eg, HBase implements splitting, partitioning, a fast
write ahead log, etc. Facebook has implemented the index directly into HBase,
which probably offers degraded indexing and search performance.
bq. We badly need the cloud features now
Right, many users are going with Elastic Search for the reasons mentioned.
> CommComponent abstracted
> ------------------------
>
> Key: SOLR-1431
> URL: https://issues.apache.org/jira/browse/SOLR-1431
> Project: Solr
> Issue Type: Improvement
> Components: search
> Affects Versions: 4.0
> Reporter: Jason Rutherglen
> Assignee: Noble Paul
> Fix For: 4.0
>
> Attachments: SOLR-1431.patch, SOLR-1431.patch, SOLR-1431.patch,
> SOLR-1431.patch, SOLR-1431.patch, SOLR-1431.patch, SOLR-1431.patch,
> SOLR-1431.patch, SOLR-1431.patch, SOLR-1431.patch, SOLR-1431.patch
>
>
> We'll abstract CommComponent in this issue.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
