-
Notifications
You must be signed in to change notification settings - Fork 344
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
Getting Error: indexed key of unsupported type or exceeded length: can not create index #1922
Comments
Hi @iSRIDHARRAO I believe that you are missing some part of the sql statement, since we can't see the Anyway, there is a limit of 512 bytes on key length for indexes. So you can't create an index where the sum of the length of its parts is more than 512 bytes, and I believe that you are just above that. |
Hi @SimoneLazzaris ,
I wanted to know that this limit was added recently or was there before in 1.4 too |
Hi @iSRIDHARRAO, the max key length limit was there already. The reason to set a limit is due to performance, the longer the keys the worst the performance you will get reading and writing data. |
Getting indexed key of unsupported type or exceeded length: can not create index using columns '[userid iudxid time api]'. Max key length is 512 error while creating an index in immudb:1.9DOM.2 container
Used the following python snippet
Earlier we used codenotary/immudb:1.4.1 image and deployed immudb, at that time index got created but now when we are using the recently released image ( immudb:1.9DOM.2 ) we are getting the error
The text was updated successfully, but these errors were encountered: