QueryHint
Related Doc:
package snappydata
Query hint for SQL queries to serialize STRING type as CLOB rather than as VARCHAR.
Query hint for SQL queries to serialize STRING type as CLOB rather than as VARCHAR.
Possible values are valid column names in the tables/schema. Multiple column names to be comma separated. One can also provide '*' for serializing all the STRING columns as CLOB.
Example:
SELECT id, name, addr, medical_history FROM t1 --+ columnsAsClob(addr)
SELECT id, name, addr, medical_history FROM t1 --+ columnsAsClob(*)
Query hint for SQL queries to serialize complex types (ARRAY, MAP, STRUCT) as CLOBs in JSON format for routed JDBC/ODBC queries rather than as serialized blobs to display better in external tools.
Query hint for SQL queries to serialize complex types (ARRAY, MAP, STRUCT) as CLOBs in JSON format for routed JDBC/ODBC queries rather than as serialized blobs to display better in external tools.
Possible values are 'true/1' or 'false/0'
Example:
SELECT * FROM t1 --+ complexTypeAsJson(1)
Query hint followed by table to override optimizer choice of index per table.
Query hint followed by table to override optimizer choice of index per table.
Possible values are valid indexes defined on the table.
Example:
SELECT * FROM t1 /*+ index(xxx) */, t2 --+ withIndex(yyy)
Query hint after FROM clause to indicate following tables have join order fixed and optimizer shouldn't try to re-order joined tables.
Query hint after FROM clause to indicate following tables have join order fixed and optimizer shouldn't try to re-order joined tables.
Possible comma separated values are io.snappydata.JOS.
Example:
SELECT * FROM /*+ joinOrder(fixed) */ t1, t2
SQL query hints as interpreted by the SnappyData SQL parser. The format mirrors closely the format used by Hive,Oracle query hints with a comment followed immediately by a '+' and then "key(value)" for the hint. Example:
SELECT * /
*+ hint(value) */FROM t1