Use different consistency levels for read and write operations

[kevinpotgieter]

…tency levels when applying schema updates.

Changes address issue: #23

[jsravn]

Adding lombok is quite a big change and probably deserves its own PR and discussion. We were trying to stick with core java w/ minimal dependencies.

edit: After talking with the guys, there is agreement we probably don't want lombok in cqlmigrate. It will bleed into all projects that depend on cqlmigrate - which may be okay for sky internal, but not as an open source public project. We spent a lot of time removing dependencies before open sourcing previously.

[jsravn]

Does it really need to be flexible? Can we instead just make schema updates WRITE=ALL and READ=ONE for everyone as a default?

We could keep it flexible, but it means that users can break it if they don't know what they're doing, and our tests are invalid for custom use cases. If we keep it flexible, I think we should:

• Change defaults to ALL/ONE (since ALL/ALL is broken)
• Add a warning if R+W < replicas (if not too difficult)

[kevinpotgieter]

Thats a fair point RE introducing lombok. We'll remove the library dependency, and provide the boiler plate code back again.

[kevinpotgieter]

We'll also remove the ability for the used to provide the consistency levels, and introduce the defaults of write=ALL and read=LOCAL_ONE i.s.o ONE?

[oliverlockwood]

@jsravn anything further from your side?

[jsravn]

I'll have a look with @chbatey.

On Thu, 18 Feb 2016 8:31 am Oliver Lockwood notifications@github.com wrote:

@jsravn https://github.com/jsravn anything further from your side?

— Reply to this email directly or view it on GitHub https://github.com/sky-uk/cqlmigrate/pull/24#issuecomment-185596801.

[oliverlockwood]

@jsravn @chbatey ping?

[jsravn]

We'll take a look today.

[jsravn]

@oliverlockwood Any idea why the build failed?