Query planner does not route routed queries to the proper keyspace

[frouioui]

Overview of the Issue

When using routed queries, the planner does not route them to the proper keyspace.

Reproduction Steps

Use the following onecase.json:

[
  {
    "comment": "Add your test case here for debugging and run go test -run=One.",
    "query": "select * from main.route2 where id > 2",
    "plan": {

    }
  }
]

Modify the routing rules (schema.json) to have:

...
      {
        "from_table": "route2",
        "to_tables": [
          "user.unsharded"
        ]
      },
...

Run TestOne. The plan output we get is:

{
  "Instructions": {
    "FieldQuery": "select * from route2 where 1 != 1",
    "Keyspace": {
      "Name": "main",
      "Sharded": false
    },
    "OperatorType": "Route",
    "Query": "select * from route2 where id > 2",
    "Table": "route2",
    "Variant": "Unsharded"
  },
  "Original": "select * from main.route2 where id > 2",
  "QueryType": "SELECT"
}

Which incorrectly routes the routed query to keyspace main instead of user.

Binary Version

17, 18, 19, main

Operating System and Environment details

n/a

Log Fragments

No response

[harshit-gangal]

This is not an issue. The query is wrong here as route2 does not belong to main keyspace as per the vschema.