[MDEV-4000] Mapping between Cassandra blob (BytesType) and MySQL BLOB does not work Created: 2013-01-04  Updated: 2013-05-27  Resolved: 2013-05-20

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: 10.0.1
Fix Version/s: 10.0.3

Type: Bug Priority: Minor
Reporter: Elena Stepanova Assignee: Sergei Petrunia
Resolution: Fixed Votes: 0
Labels: cassandra

Issue Links:
Relates
relates to MDEV-431 Cassandra storage engine Closed

 Description   

Specification in the KB says that there should be mapping between MySQL BLOB and Cassandra blob (https://kb.askmonty.org/en/cassandra-storage-engine/). It doesn't seem to work:

cqlsh:manual_test> create columnfamily cf13 ( rowkey int primary key, b blob );

[default@manual_test] describe cf13;  
    ColumnFamily: cf13
      Key Validation Class: org.apache.cassandra.db.marshal.Int32Type
      Default column value validator: org.apache.cassandra.db.marshal.UTF8Type
      Columns sorted by: org.apache.cassandra.db.marshal.UTF8Type
      GC grace seconds: 864000
      Compaction min/max thresholds: 4/32
      Read repair chance: 0.1
      DC Local Read repair chance: 0.0
      Replicate on write: true
      Caching: KEYS_ONLY
      Bloom Filter FP chance: default
      Built indexes: []
      Column Metadata:
        Column Name: b
          Validation Class: org.apache.cassandra.db.marshal.BytesType
      Compaction Strategy: org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy
      Compression Options:
        sstable_compression: org.apache.cassandra.io.compress.SnappyCompressor

create table t13 (rowkey int primary key, b blob ) ENGINE=CASSANDRA `keyspace`='manual_test' `column_family`='cf13';
ERROR 1928 (HY000): Internal error: 'Failed to map column b to datatype org.apache.cassandra.db.marshal.BytesType'

VARBINARY works:

create table t13 (rowkey int primary key, b varbinary(1024) ) ENGINE=CASSANDRA `keyspace`='manual_test' `column_family`='cf13';
# Query OK, 0 rows affected (0.04 sec)

revision-id: psergey@askmonty.org-20121224043622-xn8g8y3vhtu1lb3w
revno: 3459
branch: 10.0-base-cassandra

Maybe it requires additional options in column family specification? In this case it would be good to document them.


Generated at Thu Feb 08 06:52:57 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.