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

David Smiley commented on SOLR-16812:
-------------------------------------

This issue introduced partial support for CBOR but not for SolrJ and thus not 
generally within Solr either (not a complaint!  Progress not perfection).  
Looking at SolrExampleCborTest shows there's a large implementation gap.  
[~noble.paul] as you understand the issue well (I see in one of your comments 
above), maybe you could file an issue that recognizes this and maybe offers 
some pointers for anyone who might want to take up this task?  I'd like to see 
retiring javabin in place of CBOR on Solr's 
[roadmap|https://cwiki.apache.org/confluence/display/SOLR/Roadmap] but need a 
jira issue to capture what needs to happen.

> Support CBOR format for update/query
> ------------------------------------
>
>                 Key: SOLR-16812
>                 URL: https://issues.apache.org/jira/browse/SOLR-16812
>             Project: Solr
>          Issue Type: Task
>            Reporter: Noble Paul
>            Assignee: Noble Paul
>            Priority: Major
>             Fix For: 9.3
>
>          Time Spent: 3h 20m
>  Remaining Estimate: 0h
>
> Javabin is quite efficient and fast . But non-java users have to use JSON 
> exclusively
>  
> [CBOR |http://example.com/] is a widely used format that is supported by most 
> languages. 
>  
> Here is a benchmark of updating using CBOR vs. JSON our films.json
> {code:java}
> Payload Size (bytes)
> ============
>  
> json : 633600
> cbor : 210439  
> javabin: 234520
> time taken to index
> ====================
> JSON: 330ms
> JAVABIN: 216ms
> CBOR: 200ms
> time takes to query *:* 1100 docs
> ==================================
> json: 85 ms
> javabin : 64ms 
> cbor : 53ms{code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to