Ideally, 3500 values in ³IN" should not cause a StackOverflowError; we doubt there was something went wrong (maybe Kylin maybe a third-party lib); Anyway, if you see the error again, please help to capture the full stack trace and then send to us; Thanks for your input!
On 3/18/15, 10:57 AM, "dong wang" <[email protected]> wrote: >shaofeng, after adding the JAVA_OPTS, the StackOverflowError is GONE, it >can return the correct result but about 10s latency time, then we >optimize >the sql, of course, which has no that much values in the "IN" condition >for the select statement, previous, we have about 3500 values in the IN >condition
