Skip to content

Conversation

Kami
Copy link
Contributor

@Kami Kami commented Sep 20, 2013

This implements a solution described in #37.

This branch allows user to write a blob field value using a Python bytearray type. This is an only supported method for writing blobs when using Cassandra 2.0 and above.

With older versions (1.2 and lower), user can use an existing approach (specifying a blob value using a hex encoded string) plus this approach.

Ideally, we would discourage "bad" practices (maybe by putting a note in the docs / readme) and advise users to use bytearray approach which works with both versions.

Copy link
Member

Choose a reason for hiding this comment

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

Should this only map the first two parts? 3.0.X = 1.2, 3.1.X = 2.0?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@JeremiahDJordan Yeah, I could do that.

I wonder I should use a different / better approach thought. I guess I could also just do SELECT cql_version, release_version FROM local in the System keyspace.

What do you think?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@JeremiahDJordan I've changed it to use system.local column family in f1f329d.

I think this approach is a lot better and nicer than the other one.

Instead of using cql_version Cluster constructor argument query the "system.local" table.
This seems like a useful functionality so make it more easier to re-use this
information.
@thobbs thobbs merged commit 9627be7 into datastax:master Sep 24, 2013
@thobbs
Copy link
Contributor

thobbs commented Sep 24, 2013

I made some minor adjustments and merged it in to master. Thanks!

@Kami
Copy link
Contributor Author

Kami commented Sep 24, 2013

Sweet, thanks :)

aboudreault added a commit that referenced this pull request Jan 14, 2020
PYTHON-1192: Insights fail to serialize the startup message when the SSL Context is from PyOpenSSL
TheRealFalcon pushed a commit that referenced this pull request Jan 17, 2020
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.

3 participants