fix vpc protocol field to match vpc original declaration: (#168)

* Protocol column is INT32 in VPC doc but Athena create table uses BIGINT which I think our integration refers to VPC doc: https://docs.aws.amazon.com/vpc/latest/userguide/flow-logs.html#flow-log-records * Athena doc: https://docs.aws.amazon.com/athena/latest/ug/vpc-flow-logs.html * Integration code: https://github.com/opensearch-project/opensearch-catalog/blob/main/integrations/observability/amazon_vpc_flow/assets/create_table_vpc_schema-1.0.0.sql#L9 Signed-off-by: YANGDB <[email protected]>
opensearch-project · Jun 28, 2024 · cf2e886 · cf2e886
1 parent eace3a5
commit cf2e886
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/integrations/observability/amazon_vpc_flow/amazon_vpc_flow-1.0.0.json b/integrations/observability/amazon_vpc_flow/amazon_vpc_flow-1.0.0.json
@@ -1,6 +1,6 @@
 {
   "name": "amazon_vpc_flow",
-  "version": "1.1.0",
+  "version": "1.1.1",
   "displayName": "Amazon VPC",
   "description": "Monitor IP traffic with VPC Flow Logs.",
   "license": "Apache-2.0",

diff --git a/integrations/observability/amazon_vpc_flow/assets/create_table_vpc_schema-1.0.0.sql b/integrations/observability/amazon_vpc_flow/assets/create_table_vpc_schema-1.0.0.sql
@@ -6,7 +6,7 @@ CREATE EXTERNAL TABLE IF NOT EXISTS {table_name} (
     dstaddr string,
     srcport int,
     dstport int,
-    protocol bigint,
+    protocol int,
     packets bigint,
     bytes bigint,
     start bigint,