feat: add QueryContext to RegionRequestHeader

Author: Kelvinyu1117

c++/greptime/v1/common.pb.cc

@@ -113,6 +113,40 @@ enum ColumnDataType {
   DECIMAL128 = 30;
 }
 
+enum SqlDialect {
+  MYSQL = 0;
+  POSTGRES = 1;
+  GREPTIMEDB = 2;
+}
+
+enum PostgresByteaOutputValue {
+  HEX = 0;
+  ESCAPE = 1;
+}
+
+enum PostgresDateTimeStyle {
+  ISO = 0;
+  SQL = 1;
+  Postgres = 2;
+  German = 3;
+}
+
+enum PostgresDateOrder {
+  MDY = 0;
+  DMY = 1;
+  YMD = 2;
+}
+
+message PostgresDateStyleFormat {
+  PostgresDateTimeStyle date_style = 1;
+  PostgresDateOrder date_order = 2;
+}
+
+message ConfigurationVariables {
+  PostgresByteaOutputValue bytea_output = 1; 
+  PostgresDateStyleFormat datestyle_format = 2;
+}
+
 message IntervalMonthDayNano {
   int32 months = 1;
   int32 days = 2;

c++/greptime/v1/common.pb.h

@@ -26,14 +26,24 @@ import "greptime/v1/ddl.proto";
 
 service Region { rpc Handle(RegionRequest) returns (RegionResponse); }
 
+message QueryContext {
+  string current_catalog = 1;
+  string current_schema = 2;
+  string current_user = 3;
+  string timezone = 4;
+  map<string, string> extension = 5;
+  SqlDialect sql_dialect = 6;
+  ConfigurationVariables configuration_parameter = 7;
+}
+
 message RegionRequestHeader {
   // Encoded trace_id & span_id, follow the w3c Trace Context
   // https://www.w3.org/TR/trace-context/#header-name
   map<string, string> tracing_context = 5;
   // DB Name of request, tracking only
   string dbname = 3;
-  // The `timezone` for the request
-  string timezone = 4;
+  // The contextual information of the query
+  QueryContext query_context = 6;
 }
 
 message RegionRequest {