Github user HeartSaVioR commented on a diff in the pull request:
https://github.com/apache/storm/pull/1714#discussion_r80478720
--- Diff:
external/sql/storm-sql-core/src/test/org/apache/storm/sql/compiler/TestCompilerUtils.java
---
@@ -153,6 +158,29 @@ public static CalciteState sqlOverNestedTable(String
sql)
.field("MAPFIELD", SqlTypeName.ANY)
.field("NESTEDMAPFIELD", SqlTypeName.ANY)
.field("ARRAYFIELD", SqlTypeName.ANY)
+
+ // TODO: replace field definitions with belows while
Calcite can handle properly
--- End diff --
For me, type safely is more important than convenience. That's why we use
static typing language, and also trying to restrict more by generic and so.
IMO, we shouldn't rely Calcite to handle operators with 'ANY' type properly. If
it can handle operators properly, it's more than essential feature.
As I commented earlier we can't keep the current syntax until we modify
Calcite, or back to ExprCompiler which I really don't want to.
For now I'll try to CAST to 'ANY' explicitly and see it makes nested
multi-level access possible.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
