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

removal of the 4GB index size limit for string/JSON fields #6

Open
pakud opened this Issue Sep 19, 2017 · 4 comments

Comments

Projects
None yet
4 participants
@pakud
Copy link

pakud commented Sep 19, 2017

it would be great if the current, per index limit of 4GB for the total size of string/JSON fields was removed. currently sharding is the only workaround.

if needed i can provide a sample XML that cannot be correctly indexed because of this limit.

thanks!

@tomatolog

This comment has been minimized.

Copy link
Contributor

tomatolog commented Sep 19, 2017

Is that XML sample collection Strings or JSON collection?

@pakud

This comment has been minimized.

Copy link

pakud commented Sep 19, 2017

in this particular case the total size of <sphinx:attr type="json" name="XYZ"/> is much larger than other string / bigintint / int fields.

@tomatolog

This comment has been minimized.

Copy link
Contributor

tomatolog commented Sep 21, 2017

could you put your collection to our write only ftp at 88.99.251.227
user: manticorebugs
pass: shithappens

@pakud

This comment has been minimized.

Copy link

pakud commented Sep 23, 2017

uploaded in /issue-6

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment