Skip to content

Mismatch between Astra DB and HCD for dropping a collection from a nonexistent keyspace #1186

@hemidactylus

Description

@hemidactylus

Tested (today) on Astra DB with 1.0.12 VS HCD stargateio/data-api:v1.0.12 (on top of datastax/hcd:1.0.0-early-preview).

Dropping a collection on a keyspace that does not exist results in:

  • {"ok": 1} on HCD
  • (error) Unknown keyspace ... on Astra DB

This discrepancy is probably unintentional (?).

For context, trying the same drop on HCD through cql console does error out:

cassandra@cqlsh> drop table scytodes.notable;
InvalidRequest: Error from server: code=2200 [Invalid query] message="Table 'scytodes.notable' doesn't exist"

Metadata

Metadata

Assignees

No one assigned

    Labels

    On HoldNot ready for active development

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions