On Thu, Dec 6, 2012 at 12:03 PM, Mark Miller <markrmil...@gmail.com> wrote:
> Yeah, the main problem with it didn't really occur to me until I saw the
> properties shard in the cluster view.
>
> I started working on the UI to ignore it the other day and then never got
> there because I was getting all sorts of weird 'busy' errors from svn for a
> while and didn't have a clean checkout.
It occurs to me that the introduction of this "properties" value is
actually a back compat break anyway (since older clients won't know
it's not a real shard).
Seems like we should just bite the bullet and do it right.
{"collection1": {
"config" : "myconf"
"router" : "compositeId",
"shards" : {
"shard1" : {...
-Yonik
http://lucidworks.com
> - mark
>
> On Dec 6, 2012, at 8:16 AM, Yonik Seeley <yo...@lucidworks.com> wrote:
>
>> On Wed, Dec 5, 2012 at 5:17 PM, Mark Miller <markrmil...@gmail.com> wrote:
>>> See the custom hashing issue - the UI has to be updated to ignore this.
>>>
>>> Unfortunately, it seems that clients have to be hard coded to realize
>>> properties is not a shard unless we add another nested layer.
>>
>> Yeah, I talked about this a while back, but no one bit...
>> https://issues.apache.org/jira/browse/SOLR-3815?focusedCommentId=13452611&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13452611
>>
>> At this point, I suppose we could still add it, but retain the ability
>> to read older cluster states?
>>
>> -Yonik
>> http://lucidworks.com
>
