search

scylladb / scylla-cqlsh

A fork of the cqlsh code
Apache License 2.0
16 stars 32 forks source link

stop retruning status_code=2 on schema disagreement #57

Closed fruch closed 11 months ago

fruch commented 1 year ago

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/scylla-cqlsh#34

avikivity commented 1 year ago

title is confused

roydahan commented 11 months ago

Why is this PR stuck here for so long? Who is the maintainer here?

fruch commented 11 months ago

Why is this PR stuck here for so long? Who is the maintainer here?

currently me and @Lorak-mmk

it's stuck cause it's forgotten, and people keep opening an issue on scylla for this.

mykaul commented 11 months ago

Why is this PR stuck here for so long? Who is the maintainer here?

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.

fruch commented 11 months ago

Why is this PR stuck here for so long? Who is the maintainer here?

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: https://github.com/scylladb/scylladb/issues/13299

this was based on information there, the discussion there went to all kind of places, not suggesting any fix whatsoever.