Search

1 to 10 of 127
Sort by

Web Page
dictionary


Discussion Post
TApplicationException: String too long for dictionary encoding.

TApplicationException : String too long for dictionary



Discussion Reply
RE: TApplicationException: String too long for dictionary encoding.

Thanks Guys I truncated any text field > 32767 and used text encoding dict(32) and all good



Discussion Reply
RE: TApplicationException: String too long for dictionary encoding.

it `Encoding None`, i.e. non-dictionary


Discussion Reply
RE: TApplicationException: String too long for dictionary encoding.

Hi @Michael Kay , The max length of a string is 32767 whatever the encoding you are using, since 3.2.0 release as you can read here https://www.omnisci.com/docs/latest/7 0 release.html#id84 If you try to inject a longer string, an error occurs as you can observe into the log file E0426 17:23:03...



Discussion Reply
RE: Exception: Cast from dictionary-encoded string to none-encoded would be slow

Hi, --allow-cpu-retry and --enable-watchdog=false are compatible, if I understand your question. watchdog=false will potentially allow more high memory (more than can fit on the GPU’s) to be executed which will cause swapping of memory in the GPU. It really depends on your queries and your...


Discussion Reply
RE: Exception: Cast from dictionary-encoded string to none-encoded would be slow

I found in another post how to successfully disable watchdog : the test for this query is successful. But I would like to use --allow-cpu-retry as a way to manage datasets not fitting in GPU, in order to use also the CPU RAM: Are --allow-cpu-retry and --enable-watchdog=false alternatives? ...