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

ElasticSearch plugin is limited to 256 bytes for FULL TEXT INDEX search #5028

Open
wdroste opened this issue Dec 9, 2022 · 0 comments
Open
Labels
type/enhancement Type: make the code neat or more efficient

Comments

@wdroste
Copy link

wdroste commented Dec 9, 2022

Introduction
According to the documentation, there's a limitation on FULL TEXT INDEX of 256 bytes which is the same as the existing index. However as user I want to index long text like description, comment, or 'issue' which is inline with something like ElasticSearch where the text is much longer than 256 and is tokenized for FULL TEXT searching.

Contents
FULL TEXT index should just be a pass through to the plugin, truncating it before it gets there limits its functionality.

@wdroste wdroste added the type/enhancement Type: make the code neat or more efficient label Dec 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/enhancement Type: make the code neat or more efficient
Projects
None yet
Development

No branches or pull requests

1 participant