As our project looks ahead to the V2 API, I'd like us to consider this API being a moment for us to make other API decisions that strictly speaking are another concern outside the goals of V2. The fact that V2 is labelled as "experimental" and won't be done until Solr 11 gives us some freedom for this API.
In our Roadmap a month or more ago in "Future Possibilities", I included: "Transition from javabin to CBOR via Jackson". The important part here is less about CBOR and more about the long term discontinuation of "javabin". I propose that javabin is no longer supported in the V2 APIs. Perhaps a feature-flag to opt-in while it still clings to life but not really "supported" and so may be under-tested and might change or break release-to-release while it still exists. Users should use XML or JSON or JSON equivalents like CBOR[2] or Smile[3]. FYI CBOR is only partially in Solr right now. This proposal doesn't affect V1 at all. This is easily a reversible decision should we realize javabin is needed in V2. WDYT? [1] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=158871392#Roadmap-Futurepossibilities [2] https://solr.apache.org/guide/solr/latest/query-guide/response-writers.html#cbor-response-writer [3] https://solr.apache.org/guide/solr/latest/query-guide/response-writers.html#smile-response-writer ~ David Smiley Apache Lucene/Solr Search Developer http://www.linkedin.com/in/davidwsmiley
