Thanks Paulo for sharing the JIRA !! I have added my comments there.
"It is not advisable to remain with a down node for a long time without
replacing it (with risk of not being able to achieve consistency if another
node goes down)."
I am referring to a generic scenario where a cluster may affor
Solr string fields (solr.StrField) are not tokenized, so they do not have
analyzers. That means they will be case-sensitive.
Regex is introduced with slash characters, so you appear to be performing a
wildcard query instead.
Typically, you would make a copy of such a Cassandra text field (using
)
I think the requirement was stated that old versions will be kept, which is
consistent with Cassandra and the LSM data model - it would avoid the need
for compactions of the actual chunked blob data.
Throughput mostly comes down to adequately provisioning your cluster.
-- Jack Krupansky
On Wed,
Thanks Paulo for sharing the JIRA !! I have added my comments there.
"It is not advisable to remain with a down node for a long time without
replacing it (with risk of not being able to achieve consistency if another
node goes down)."
I am referring to a generic scenario where a cluster may affor
The answer to this questions is very much dependent on the throughput,
desired latency and access patters (R/W or R/O)? In general what I have
seen working for high throughput environment is to either use a distributed
file system like Ceph/Gluster or object store like S3 and keep the pointer
in th
There's also the 'support' issue.. C* is hard enough as it is... maybe you
can bring in another system like ES or HDFS but the more you bring in the
more your complexity REALLY goes through the roof.
Better to keep things simple.
I really like the chunking idea for C*... seems like an easy way to
