[
https://issues.apache.org/jira/browse/CASSANDRA-14872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17040725#comment-17040725
]
Dinesh Joshi commented on CASSANDRA-14872:
------------------------------------------
Thanks for checking it out Andy. I considered making geomet optional. It will
need some driver changes and I am reluctant to check in a custom build of the
driver. So this is an ok compromise for the time being. As an added benefit of
leaving it in, users can use this cqlsh to connect to DSE and all features that
the driver support will continue functioning including the geospatial types.
> Update to version of python driver and update cqlsh to use driver metadata
> for virtual tables
> ---------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-14872
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14872
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/cqlsh
> Reporter: Andy Tolbert
> Assignee: Dinesh Joshi
> Priority: Normal
> Fix For: 4.0, 4.0-alpha
>
>
> When virtual tables were implemented ([CASSANDRA-7622]), cqlsh.py was updated
> to parse virtual keyspace metadata by making queries to the
> {{system_virtual_schema}} table and included a TODO:
> {code:python}
> # TODO remove after virtual tables are added to connection metadata
> {code}
> Since python driver 3.15.0 (released in August), the driver now parses
> virtual keyspace metadata. It would be good to update the bundled python
> driver and simplify cqlsh code to utilize its capability to parse virtual
> tables.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
