[ https://issues.apache.org/jira/browse/SOLR-13296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16786785#comment-16786785 ]
Cassandra Targett commented on SOLR-13296: ------------------------------------------ Since the 8.0 Ref Guide isn't out yet, IMO this should be backported into branch_8_0. I'll do that once the new 8.0 RC is out so I don't screw that process up (probably wouldn't, but just to be safest), but there's no reason to knowingly release with bad info. > Example of Preanalyzed JSON in ref guide invalid > ------------------------------------------------ > > Key: SOLR-13296 > URL: https://issues.apache.org/jira/browse/SOLR-13296 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) > Components: documentation > Affects Versions: 7.6 > Reporter: Gus Heck > Assignee: Gus Heck > Priority: Trivial > Fix For: master (9.0), 8.1 > > Attachments: SOLR-13296.patch > > > Writing a test for a use case that was pre-analyzing a field for a customer I > decided to first check that the config could successfully accept a chunk of > preanalyzed json. Thus I grabbed the example in the docs and BOOM > {code} > org.apache.solr.client.solrj.impl.CloudSolrClient$RouteException: Error from > server at http://127.0.0.1:63302/solr/testCol_shard1_replica_n1: Exception > writing document id 1 to the index; possible analysis error: startOffset must > be non-negative, and endOffset must be >= startOffset, and offsets must not > go backwards startOffset=5,endOffset=8,lastStartOffset=123 for field > 'preanalyzed' > {code} > Turns out the example has token offsets that go backwards... attaching a > patch to make the (mostly nonsensical) example at least technically valid -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org