Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Since Elasticsearch 6.0.0 offsets must not go backwards #1

Closed
orangemi opened this issue Apr 11, 2018 · 0 comments · Fixed by #2
Closed

Since Elasticsearch 6.0.0 offsets must not go backwards #1

orangemi opened this issue Apr 11, 2018 · 0 comments · Fixed by #2
Assignees

Comments

@orangemi
Copy link
Owner

since Elasticsearch 6.0.0, startOffset must be non-negative, and endOffset must be >= startOffset, and offsets must not go backwards.

That means startOffsets should be always greater than before. Although Chinese word token can be divided into servial token due to ambiguity like "中国人" can be tokenized "中国"+"人" & "中国人"

Origin Error:

    {
      "error": {
        "root_cause": [
          {
            "type": "remote_transport_exception",
            "reason": "[4YKGDw9][192.168.0.21:9305][indices:data/write/update[s]]"
          }
        ],
        "type": "illegal_argument_exception",
        "reason": "startOffset must be non-negative, and endOffset must be >= startOffset, and offsets must not go backwards startOffset=0,endOffset=3,lastStartOffset=1 for field 'description'"
      },
      "status": 400
    }

One of solution metioned below:
hankcs/hanlp-lucene-plugin#27 (comment)
hankcs/hanlp-lucene-plugin@eebea90

And origin issue reference:
sing1ee#9

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant