Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sync with upstream 3.28.0 #364

Merged
merged 20 commits into from
Nov 18, 2024

Conversation

dkropachev
Copy link
Collaborator

@dkropachev dkropachev commented Aug 9, 2024

it is a peace of #329 that updates master to 3.28.0

@dkropachev dkropachev force-pushed the dk/sync-with-upstream-3.28.0 branch 4 times, most recently from 76e1a2f to 8cc41a4 Compare August 9, 2024 22:42
@dkropachev dkropachev marked this pull request as ready for review August 9, 2024 22:45
@dkropachev dkropachev force-pushed the dk/sync-with-upstream-3.28.0 branch 2 times, most recently from 81b3b33 to e344b51 Compare August 9, 2024 23:57
@dkropachev dkropachev self-assigned this Aug 9, 2024
docs/index.rst Outdated Show resolved Hide resolved
@dkropachev dkropachev force-pushed the dk/sync-with-upstream-3.28.0 branch 4 times, most recently from 969c93b to 5357c34 Compare August 13, 2024 18:24
Copy link

@fruch fruch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@dkropachev
Copy link
Collaborator Author

@Lorak-mmk , @roydahan , is it good to go?

@Lorak-mmk
Copy link

@Lorak-mmk , @roydahan , is it good to go?

I'm reviewing right now

Copy link

@Lorak-mmk Lorak-mmk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Commits that add column encryption policy make a lot of changes.
I think it would be better to drop those commits altogether until we decide if and how we want to implement the encryption - adding code later is much easier than removing it.

After reviewing this I remember why I dislike current process so much...

docs/.nav Outdated Show resolved Hide resolved
.travis.yml Outdated Show resolved Hide resolved
setup.py Outdated Show resolved Hide resolved
cassandra/cqltypes.py Outdated Show resolved Hide resolved
cassandra/policies.py Show resolved Hide resolved
docs/.nav Outdated Show resolved Hide resolved
tox.ini Outdated Show resolved Hide resolved
@dkropachev dkropachev force-pushed the dk/sync-with-upstream-3.28.0 branch 2 times, most recently from ad15d4d to acbf507 Compare August 15, 2024 23:57
@dkropachev
Copy link
Collaborator Author

Commits that add column encryption policy make a lot of changes. I think it would be better to drop those commits altogether until we decide if and how we want to implement the encryption - adding code later is much easier than removing it.

After reviewing this I remember why I dislike current process so much...

CLE is highly integrated into cluster, session and even query, removing these commits will create unnecessary conflicts with any code done on top of it, also as bonus you are going to get a headache of merging them back and re-resolving same conflicts other way around when/if you decide to get this code in.

@dkropachev
Copy link
Collaborator Author

dkropachev commented Nov 10, 2024

Commits that add column encryption policy make a lot of changes. I think it would be better to drop those commits altogether until we decide if and how we want to implement the encryption - adding code later is much easier than removing it.

After reviewing this I remember why I dislike current process so much...

Since we have already removed docs, I can't tell you that leaving code in creates way less conflicts and makes merging so much easier.
Also we need to consider that we are not merging code that was not reviewed, it already went though review process on the upstream, in some cases, when we changed core on our side it does not mean much, but on the side of the code we did not touch it does.

Copy link

@Lorak-mmk Lorak-mmk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some minor comments, apart from that looks good.

.travis.yml Outdated Show resolved Hide resolved
docs/index.rst Outdated Show resolved Hide resolved
docs/index.rst Outdated Show resolved Hide resolved
@fruch
Copy link

fruch commented Nov 18, 2024

Docs are failing to build

https://github.com/scylladb/python-driver/actions/runs/11894706235/job/33142543012#step:6:1

There was some seriouse issues in policy implementation in `3.27.0`.
We want to inspect the feature before making it available.
@dkropachev dkropachev merged commit 416d9ae into scylladb:master Nov 18, 2024
19 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants