[
https://issues.apache.org/jira/browse/SOLR-2765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13125393#comment-13125393
]
Ted Dunning commented on SOLR-2765:
-----------------------------------
{quote}
Do you have any thoughts on the size of this file?
{quote}
Well, the prototype that I have half coded uses JSON if only because gson makes
that choice easy, but the last time that I said that big JSON is no problem was
in Mahout. After boldly making that statement, I started trying to store
models that wound up as 100MB of JSON which good GB of RAM to parse.
My current, revised position is that serialization fashions will change over
time and they should always be pluggable. As such, let's stay with what is
traditional for a bit longer. XML should not have any significant size penalty
if we both to GZIP the results and uncompressed XML or JSON both win on
readability which is the critical feature during development.
If size really is a problem, then protobufs or Avro is a better answer than
JSON anyway.
> Shard/Node states
> -----------------
>
> Key: SOLR-2765
> URL: https://issues.apache.org/jira/browse/SOLR-2765
> Project: Solr
> Issue Type: Sub-task
> Components: SolrCloud, update
> Reporter: Yonik Seeley
> Fix For: 4.0
>
> Attachments: cluster_state-file.patch, combined.patch,
> incremental_update.patch, scheduled_executors.patch, shard-roles.patch,
> solrcloud.patch
>
>
> Need state for shards that indicate they are recovering, active/enabled, or
> disabled.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
