stop retruning status_code=2 on schema disagreement #57
Conversation
|
title is confused |
fruch
force-pushed
the
warn_on_schema_change
branch
from
ffd28ae to
8de4f87
Compare
fruch
changed the title
So far if a query is executed during schema changes that takes more then 5sec to be resolved, cqlsh would print a warning and change the return status to failure. if it's just a warning, we shouldn't be failure the command. especily since after this warning we are waiting without a timeout for schema to be resolved. Fixes: scylladb#34
fruch
changed the title
fruch
force-pushed
the
warn_on_schema_change
branch
from
8de4f87 to
6912ad6
Compare
|
Why is this PR stuck here for so long? |
currently me and @Lorak-mmk it's stuck cause it's forgotten, and people keep opening an issue on scylla for this. |
There's no milestone or priority, so we cannot track it for a specific release and prioritize / de-prioritize it. |
also this one didn't had any conclusion, and doesn't have priority or target: this was based on information there, the discussion there went to all kind of places, not suggesting any fix whatsoever. |
So far if a query is executed during schema changes that takes more then 5sec to be resolved, cqlsh would print a warning and change the return status to failure.
if it's just a warning, we shouldn't be failure the command. especily since after this warning we are waiting without a timeout for schema to be resolved.
Fixes: #34