lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Miller (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-5473) Make one state.json per collection
Date Tue, 10 Dec 2013 17:03:09 GMT

    [ https://issues.apache.org/jira/browse/SOLR-5473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13844416#comment-13844416
] 

Mark Miller commented on SOLR-5473:
-----------------------------------

bq. Thanks for the suggestion.However ,I added it for my dev testing will be removed before
commit.

For that stuff, I've found that if it's useful for development, it will be useful for someone
else when they are debugging. I used to do the same thing, and every time I end up wasting
a lot of time putting it back after I take it out, uncommenting it after I comment it out
or whatever. If you just put it under debug logging, it's more powerful (you can control things
very nicely with config) and it will help you and future developers in the long run.

> Make one state.json per collection
> ----------------------------------
>
>                 Key: SOLR-5473
>                 URL: https://issues.apache.org/jira/browse/SOLR-5473
>             Project: Solr
>          Issue Type: Sub-task
>          Components: SolrCloud
>            Reporter: Noble Paul
>            Assignee: Noble Paul
>         Attachments: SOLR-5473.patch, SOLR-5473.patch, SOLR-5473.patch, SOLR-5473.patch
>
>
> As defined in the parent issue, store the states of each collection under /collections/collectionname/state.json
node



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message