Slight typo:
formerly called “composite ID routing”
should read
formerly called “implicit routing”
On Tue, Jul 25, 2017 at 9:57 AM, Walter Underwood wrote:
> Solr is not Oracle. Designs that might be great for Oracle can be terrible
> for Solr.
>
> Solr really does not do this automatically, so
Solr is not Oracle. Designs that might be great for Oracle can be terrible for
Solr.
Solr really does not do this automatically, so you won’t find that. If your job
is to find that feature, you will fail. If your job is “find or write the
feature”, you will be writing it.
As I said before, you
If you decide to go with multiple collection and aliasing, this would be
useful
https://blog.cloudera.com/blog/2013/10/collection-aliasing-near-real-time-search-for-really-big-data/
On Sat, Jul 22, 2017 at 10:37 AM, Shawn Heisey wrote:
> On 7/22/2017 5:02 AM, m rehman kahloon wrote:
> > but my
On 7/22/2017 5:02 AM, m rehman kahloon wrote:
> but my R&D is to find a way, not to use shard name using loading
> time,solrcloud automatically load data into predefined shard/date specific
> shard.
The implicit router is the only one you can use when you're doing time
interval sharding, because i
Hi Sir Walter,
Ya, you are right, i am trying to create a structure like
oracle partitioning.
each day partition like each day shard.
already creted date wise shards and loading time using specific shard name
to load data.
but my R&D is to find a way, not to use shard name using
Thanks for your response,
actually my per day data size is too big, round 400gb, so
thats why my plan to use date interval ,each shard will represent to pre
defined date. delete will not possible.
i am looking for some way, to perform automatically, loading time not give
any sha
[mailto:wun...@wunderwood.org]
Sent: Thursday, July 20, 2017 1:24 PM
To: solr-user@lucene.apache.org
Subject: Re: Need guidance solrcloud shardings with date interval
Well, you have bad problem. You have a requirement that forces you to build an
expensive, unreliable search system.
You need to
Well, you have bad problem. You have a requirement that forces you to build an
expensive, unreliable search system.
You need to do specific shard creation at specific times every day. What
happens if that fails? Does search go down until it is fixed because all
searches are going to a shard tha
bq: that is our requirmnt to load data into specific shard and later
after rentention time we will delete that shard
Why is it necessary to delete a shard when deleting the old data by
query removes it? This sounds like an XY problem. Someone has
"required" that you enforce data retention by dele
blockquote, div.yahoo_quoted { margin-left: 0 !important; border-left:1px
#715FFA solid !important; padding-left:1ex !important; background-color:white
!important; } Hi Eric,
Thank you very much for your guidance.
No sir that is our requirmnt to load data into specific shard and later after
r
Agree. One should first try to measure the performance with standard/common
approach.
On Thu, Jul 20, 2017 at 11:00 AM, Walter Underwood
wrote:
> I agree. Use the standard shard distribution and delete by query to remove
> older documents.
>
> Much, much simpler and probably faster at query time
I agree. Use the standard shard distribution and delete by query to remove
older documents.
Much, much simpler and probably faster at query time.
I’m seeing a lot of e-mails about people trying to do fancy things with
sharding before they’ve even tried and measured the performance.
wunder
Walt
Use the "implicit" router (being renamed "manual". that takes the
value of a particular field (_route_ by default) and sends docs to
that exact shard.
But I also question whether sharding on this schema is a good idea. If
you have an access pattern where most queries are for, say, the last
two day
13 matches
Mail list logo
