[jira] [Resolved] (TRAFODION-1673) Implement the WITH clause in Trafodion SQL for simple use cases
[ https://issues.apache.org/jira/browse/TRAFODION-1673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liu ming resolved TRAFODION-1673. - Resolution: Fixed initial support is done, enhancement will be done in iterations. > Implement the WITH clause in Trafodion SQL for simple use cases > --- > > Key: TRAFODION-1673 > URL: https://issues.apache.org/jira/browse/TRAFODION-1673 > Project: Apache Trafodion > Issue Type: New Feature > Components: sql-cmp >Reporter: Hans Zeller >Assignee: liu ming > Fix For: 2.1-incubating > > > We keep running into queries that use a WITH clause to define a temporary > view that can be used once or multiple times in a FROM clause in the query. > For non-recursive queries, the WITH clause could probably be handled very > similar to a view. When it is defined, we create an in-memory view > descriptor, containing the name and the definition. When it is used in a FROM > clause, we could go through a code path similar to that of a view - bind the > (temporary) view text and substitute it in the query. The fix could probably > be handled entirely in the binder. > This JIRA is *not* about recursive queries, those would require a lot more > effort, involving many components in addition to the binder. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TRAFODION-2127) enhance Trafodion implementation of WITH clause
liu ming created TRAFODION-2127: --- Summary: enhance Trafodion implementation of WITH clause Key: TRAFODION-2127 URL: https://issues.apache.org/jira/browse/TRAFODION-2127 Project: Apache Trafodion Issue Type: Improvement Reporter: liu ming TRAFODION-1673 described some details about how to support WITH clause in Trafodion. As initial implementation, we use a simple pure-parser method. That way, Trafodion can support WITH clause functionally, but not good from performance point of view, also need to enhance the parser to be more strict in syntax. This JIRA is a follow up JIRA, to track following effort to support Trafodion WITH clause. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TRAFODION-2121) add support of HIVE data type of DECIMAL
[ https://issues.apache.org/jira/browse/TRAFODION-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15390880#comment-15390880 ] ASF GitHub Bot commented on TRAFODION-2121: --- GitHub user traflm opened a pull request: https://github.com/apache/incubator-trafodion/pull/618 [TRAFODION-2121] add support of HIVE data type of DECIMAL support HIVE data type 'decimal' HIVE decimal => Trafodion decimal(10, 0) HIVE decimal(p,s) => Trafodion decimal(p,s) Please help to review. You can merge this pull request into a Git repository by running: $ git pull https://github.com/traflm/incubator-trafodion TRAFODION-2047 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-trafodion/pull/618.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #618 commit ad6c2f3eecde12fa50c95a1b8f22b53fb4534625 Author: Liu MingDate: 2016-07-23T23:58:56Z [TRAFODION-2121] add support of HIVE data type of DECIMAL > add support of HIVE data type of DECIMAL > > > Key: TRAFODION-2121 > URL: https://issues.apache.org/jira/browse/TRAFODION-2121 > Project: Apache Trafodion > Issue Type: Sub-task > Components: sql-cmp >Reporter: liu ming >Assignee: liu ming > > support hive datatype DECIMAL and DECIMAL(p,s) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TRAFODION-2047) add SQL syntax support to INTERSECT
[ https://issues.apache.org/jira/browse/TRAFODION-2047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liu ming updated TRAFODION-2047: Fix Version/s: 2.1-incubating > add SQL syntax support to INTERSECT > --- > > Key: TRAFODION-2047 > URL: https://issues.apache.org/jira/browse/TRAFODION-2047 > Project: Apache Trafodion > Issue Type: New Feature >Reporter: liu ming >Assignee: liu ming > Fix For: 2.1-incubating > > > INTERSECT is a common SQL syntax. > Trafodion should support it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TRAFODION-1713) IDs returned from IDTMSRV process should be periodically re-calibrated so that they are a better approximation of a logical time
[ https://issues.apache.org/jira/browse/TRAFODION-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Atanu Mishra updated TRAFODION-1713: Fix Version/s: 2.0-incubating > IDs returned from IDTMSRV process should be periodically re-calibrated so > that they are a better approximation of a logical time > - > > Key: TRAFODION-1713 > URL: https://issues.apache.org/jira/browse/TRAFODION-1713 > Project: Apache Trafodion > Issue Type: Improvement > Components: dtm >Affects Versions: 1.3-incubating >Reporter: Sean Broeder >Assignee: Sean Broeder > Fix For: 2.0-incubating > > > The IDs returned by the IDTMSRV process start out with an initial time value > seed based on the current time, but subsequently are just an atomic long. > Over time this value deviates greatly from any form of recognizable time > value. This works fine for the initial purpose of the server, but it could > be improved by keeping the values more closely related to a time value that > could be used as a snapshot value for queries. > A configurable timer value could be used to trigger the reseeding at an > interval that makes sense for the user such that it doesn't impact > performance and still remains relevant. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (TRAFODION-1713) IDs returned from IDTMSRV process should be periodically re-calibrated so that they are a better approximation of a logical time
[ https://issues.apache.org/jira/browse/TRAFODION-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Atanu Mishra closed TRAFODION-1713. --- Resolution: Fixed Closing on behalf of Sean. > IDs returned from IDTMSRV process should be periodically re-calibrated so > that they are a better approximation of a logical time > - > > Key: TRAFODION-1713 > URL: https://issues.apache.org/jira/browse/TRAFODION-1713 > Project: Apache Trafodion > Issue Type: Improvement > Components: dtm >Affects Versions: 1.3-incubating >Reporter: Sean Broeder >Assignee: Sean Broeder > Fix For: 2.0-incubating > > > The IDs returned by the IDTMSRV process start out with an initial time value > seed based on the current time, but subsequently are just an atomic long. > Over time this value deviates greatly from any form of recognizable time > value. This works fine for the initial purpose of the server, but it could > be improved by keeping the values more closely related to a time value that > could be used as a snapshot value for queries. > A configurable timer value could be used to trigger the reseeding at an > interval that makes sense for the user such that it doesn't impact > performance and still remains relevant. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TRAFODION-1713) IDs returned from IDTMSRV process should be periodically re-calibrated so that they are a better approximation of a logical time
[ https://issues.apache.org/jira/browse/TRAFODION-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Broeder updated TRAFODION-1713: This is fixed as part of Trafodion 2.0 > IDs returned from IDTMSRV process should be periodically re-calibrated so > that they are a better approximation of a logical time > - > > Key: TRAFODION-1713 > URL: https://issues.apache.org/jira/browse/TRAFODION-1713 > Project: Apache Trafodion > Issue Type: Improvement > Components: dtm >Affects Versions: 1.3-incubating >Reporter: Sean Broeder >Assignee: Sean Broeder > > The IDs returned by the IDTMSRV process start out with an initial time value > seed based on the current time, but subsequently are just an atomic long. > Over time this value deviates greatly from any form of recognizable time > value. This works fine for the initial purpose of the server, but it could > be improved by keeping the values more closely related to a time value that > could be used as a snapshot value for queries. > A configurable timer value could be used to trigger the reseeding at an > interval that makes sense for the user such that it doesn't impact > performance and still remains relevant. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TRAFODION-2121) add support of HIVE data type of DECIMAL
[ https://issues.apache.org/jira/browse/TRAFODION-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15390677#comment-15390677 ] liu ming commented on TRAFODION-2121: - from Hive 0.13, Decimal is changed, it is too complex to find out hive version at compile time, so Trafodion treat 'decimal' in Hive as it is after Hive0.13. and hive definitions is from https://cwiki.apache.org/confluence/display/Hive/LanguageManual+Types#LanguageManualTypes-decimal > add support of HIVE data type of DECIMAL > > > Key: TRAFODION-2121 > URL: https://issues.apache.org/jira/browse/TRAFODION-2121 > Project: Apache Trafodion > Issue Type: Sub-task > Components: sql-cmp >Reporter: liu ming >Assignee: liu ming > > support hive datatype DECIMAL and DECIMAL(p,s) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (TRAFODION-2121) add support of HIVE data type of DECIMAL
[ https://issues.apache.org/jira/browse/TRAFODION-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on TRAFODION-2121 started by liu ming. --- > add support of HIVE data type of DECIMAL > > > Key: TRAFODION-2121 > URL: https://issues.apache.org/jira/browse/TRAFODION-2121 > Project: Apache Trafodion > Issue Type: Sub-task > Components: sql-cmp >Reporter: liu ming >Assignee: liu ming > > support hive datatype DECIMAL and DECIMAL(p,s) -- This message was sent by Atlassian JIRA (v6.3.4#6332)