[
https://issues.apache.org/jira/browse/CASSANDRA-18302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17700404#comment-17700404
]
Jacek Lewandowski commented on CASSANDRA-18302:
-----------------------------------------------
I must admit that the limit I've introduced is stupid. Firstly, because
non-prepared statement only exists for the time of execution, and prepared
statement stores the whole string anyway. Therefore that limit is not really
needed.
Regarding `asCQL` there more examples which show that this is invalid, and
actually cannot be, because asCQL is applied to the read command, that is, what
we really read from the sstables/memtables. For example, for a {{select k, c, v
...}} it will print only {{select v ... }}, for a {{select ttl(v),
writetime(v)...}} it will print {{select v...}}. Also, there is no such method
for modification statements so in case of errors there the messages do not
include any pointer to the broken query - although I missed that and haven't
fixed, I can do that with easily
> Fix AIOOBE and improve validation messages for transaction statements
> ---------------------------------------------------------------------
>
> Key: CASSANDRA-18302
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18302
> Project: Cassandra
> Issue Type: Improvement
> Components: Accord
> Reporter: Jacek Lewandowski
> Assignee: Jacek Lewandowski
> Priority: Normal
> Fix For: 5.x
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> Currently it happens sometimes that ArrayIndexOutOfBoundsException is thrown
> from asCql method when validation transaction statement. In addition, asCql
> does not return precisely the query user entered so the whole error message
> can be misleading.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
