Uploaded image for project: 'Cassandra'
  1. Cassandra
  2. CASSANDRA-10145

Change protocol to allow sending key space independent of query string

Agile BoardAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Normal
    • Resolution: Fixed
    • 4.0-alpha1, 4.0
    • None
    • Clients

    Description

      Currently keyspace is either embedded in the query string or set through "use keyspace" on a connection by client driver.

      There are practical use cases where client user has query and keyspace independently. In order for that scenario to work, they will have to create one client session per keyspace or have to resort to some string replace hackery.

      It will be nice if protocol allowed sending keyspace separately from the query.

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            stamhankar999 Sandeep Tamhankar Assign to me
            vkasar Vishy Kasar
            Sandeep Tamhankar
            Robert Stupp
            Votes:
            1 Vote for this issue
            Watchers:
            10 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment