cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sam Tunnicliffe (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-8553) Add a key-value payload for third party usage
Date Fri, 20 Mar 2015 09:06:39 GMT


Sam Tunnicliffe commented on CASSANDRA-8553:

{{QueryHandler}} is all about _doing_ something with statements, rather than building them
in the first place. That {{process()}} accepts a string and encapsulates the parsing is just
a convenience really, so I don't see a whole lot of value in making extra work for QH implementers
by exposing {{parse()}} directly.
I guess it's possible (though unlikely) that a custom QH might be doing something fancy with
prepared statement caches, so perhaps adding  {{preparedStatementCount()}} is more ok (though
I don't feel strongly about that either really).
I do agree about {{CQLSStableWriter}}, and would stick with using {{QueryProcessor}} directly

> Add a key-value payload for third party usage
> ---------------------------------------------
>                 Key: CASSANDRA-8553
>                 URL:
>             Project: Cassandra
>          Issue Type: Sub-task
>            Reporter: Sergio Bossa
>            Assignee: Robert Stupp
>              Labels: client-impacting, protocolv4
>             Fix For: 3.0
>         Attachments: 8553-v2.txt, 8553.txt
> An useful improvement would be to include a generic key-value payload, so that developers
implementing a custom {{QueryHandler}} could leverage that to move custom data back and forth.

This message was sent by Atlassian JIRA

View raw message