CQLTypeParser::IncompleteTypeError

[vroyer]

When using the logstash-output-cassandra plugin with elassandra 2.4.2-5 (https://github.com/strapdata/elassandra) , i get the following error when the keyspace kibana defines the following User Defined Type.

Pipeline aborted due to error {:exception=>"Cassandra::Cluster::Schema::CQLTypeParser::IncompleteTypeError"
Host 127.0.0.1 closed connection (Cassandra::Errors::IOError: unable to lookup type "\"visualization_kibanaSavedObjectMeta\"") {:level=>:debug, :file=>"cassandra/cluster/connector.rb", :line=>"341", :method=>"disconnected"}

Kibana keyspace is not really uses by logstash but automatically discovered by the cassandra driver. This probably a cassandra driver issue. Elassandra 2.4.2-5 rely on Cassandra 3.0.10.

CREATE TYPE kibana."visualization_kibanaSavedObjectMeta" (
    "searchSourceJSON" frozen<list<text>>
);

CREATE TABLE kibana.visualization (
    "_id" text PRIMARY KEY,
    description list<text>,
    "kibanaSavedObjectMeta" list<frozen<"visualization_kibanaSavedObjectMeta">>,
    "savedSearchId" list<text>,
    title list<text>,
    "uiStateJSON" list<text>,
    version list<int>,
    "visState" list<text>
) WITH bloom_filter_fp_chance = 0.01
    AND caching = {'keys': 'ALL', 'rows_per_partition': 'NONE'}
    AND comment = 'Auto-created by Elassandra'
    AND compaction = {'class': 'org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy', 'max_threshold': '32', 'min_threshold': '4'}
    AND compression = {'chunk_length_in_kb': '64', 'class': 'org.apache.cassandra.io.compress.LZ4Compressor'}
    AND crc_check_chance = 1.0
    AND dclocal_read_repair_chance = 0.1
    AND default_time_to_live = 0
    AND gc_grace_seconds = 864000
    AND max_index_interval = 2048
    AND memtable_flush_period_in_ms = 0
    AND min_index_interval = 128
    AND read_repair_chance = 0.0
    AND speculative_retry = '99PERCENTILE';

[valentin-fischer]

Interesting project that elassandra thing....

Regarding the actual issue, what LS version are you using ?
In my case using cassandra => 2.2.4 with LS => 2.4.1-1

[vroyer]

Logstash 2.4.0 Thanks.

…

Le 27 janv. 2017 à 11:41, Valentin Fischer ***@***.***> a écrit : Interesting project that elassandra thing.... Regarding the actual issue, what LS version are you using ? In my cause using cassandra => 2.2.4 with LS => 2.4.1-1 — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#7 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AJzHmeE9Wcv5BRxgtsg8200N34prS2f0ks5rWcnrgaJpZM4LtoJw>.

[valentin-fischer]

Did you try also => https://github.com/PerimeterX/logstash-output-cassandra ?

[vroyer]

Yes, i have cloned the plugin from this repository : $ git remote -v origin https://github.com/PerimeterX/logstash-output-cassandra (fetch) origin https://github.com/PerimeterX/logstash-output-cassandra (push)

…

Le 27 janv. 2017 à 12:38, Valentin Fischer ***@***.***> a écrit : Did you try also => https://github.com/PerimeterX/logstash-output-cassandra <https://github.com/PerimeterX/logstash-output-cassandra> ? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#7 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AJzHmQF6ULreH_100tqjw4WtIhisFSFlks5rWdc8gaJpZM4LtoJw>.

[vroyer]

This is a cassandra ruby driver issue, see https://datastax-oss.atlassian.net/browse/RUBY-291
It would require an upgrade to the fixed driver version when available.

[vroyer]

The ruby cassandra driver version 3.1.1 is now fixed (see https://datastax-oss.atlassian.net/browse/RUBY-291 ) and this will solve this issue.