[
https://issues.apache.org/jira/browse/SOLR-11542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16224345#comment-16224345
]
David Smiley commented on SOLR-11542:
-------------------------------------
The parent issue here is SOLR-11299 "Time partitioned collections (umbrella
issue)"; please read the first comment, first paragraph which briefly mentions
two ways to go about this, with a reference to SOLR-9562 as having background
discussion on the merits of both approaches. Multiple people had their take,
which is nice to see.
There's definitely a trade-off and I don't think it's an obvious choice.
Purely from a coding/implementation perspective, I'd much prefer to go with
shard based partitions and thus a custom DocRouter amongst other things. It
leverages Solr's internals better. But from a practical / requirements
perspective & scale, I think collection based partitions will satisfy more
users -- especially when you consider the ability to have collections that
themselves have numShards > 1.
I don't want to leave things more complex than what they were, to the extent I
can help it. I improved some collection alias handling in SOLR-11444 which was
related to this stuff. With regards to DURP, Gus and I have made some minor
improvements; I'm sure more could be done. In this issue here, I don't want to
add more LOC to DURP; instead very likely a helper of sorts, not unlike how
DURP has such helpers/collaborators already like AtomicUpdateDocumentMerger.
Perhaps an additional URP preceding DURP could be done alternatively but
nonetheless some tweaks to DURP will be needed either way. I'm looking closer
at the details tomorrow.
> Add feature to DistributedURP to route time partitioned collections
> -------------------------------------------------------------------
>
> Key: SOLR-11542
> URL: https://issues.apache.org/jira/browse/SOLR-11542
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud
> Reporter: David Smiley
> Fix For: 7.2
>
>
> Assuming we have some time partitioning metadata on an alias (see SOLR-11487
> for the metadata facility), we'll then need to route documents to the right
> collection. I tentatively propose a helper class to DistributedURP to do
> this. Perhaps a separate URP is plausible, though it will take some
> modifications to DistributedURP.
> The scope of this issue is:
> * decide on some alias metadata names & semantics
> * decide the collection suffix pattern. Read/write code (needed to route).
> * the routing code
> No new partition creation nor deletion happens is this issue.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
