[ 
https://issues.apache.org/jira/browse/TRAFODION-2439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828545#comment-15828545
 ] 

ASF GitHub Bot commented on TRAFODION-2439:
-------------------------------------------

Github user anoopsharma00 commented on a diff in the pull request:

    https://github.com/apache/incubator-trafodion/pull/913#discussion_r96706601
  
    --- Diff: core/sql/optimizer/BindRelExpr.cpp ---
    @@ -13445,6 +13435,14 @@ RelExpr * GenericUpdate::bindNode(BindWA *bindWA)
       if (getOperatorType() == REL_UNARY_UPDATE ||
           getOperatorType() == REL_UNARY_DELETE) {
     
    +    if (getTableDesc()->getNATable()->isHiveTable())
    +      {
    +        *CmpCommon::diags() << DgSqlCode(-4223)
    +                            << DgString0("Update/Delete on Hive table is");
    +        bindWA->setErrStatus();
    +        return this;
    +      }
    +
    --- End diff --
    
    
    During binder phase, relational nodes are typed as REL_UNARY_UPDATE or 
REL_UNARY_DELETE
    for update or delete operations. Binder checks for them to determine if it 
is an update or delete.
    They may later get changed to other upd/del like subset/unique/cursor etc.
    No update or delete operations are currently supported on hive tables.
    



> add/externalize support to create trafodion views on hive tables
> ----------------------------------------------------------------
>
>                 Key: TRAFODION-2439
>                 URL: https://issues.apache.org/jira/browse/TRAFODION-2439
>             Project: Apache Trafodion
>          Issue Type: New Feature
>            Reporter: Anoop Sharma
>            Assignee: Anoop Sharma
>            Priority: Minor
>
> this enhancement is to add support for creating views  on hive tables.
> Views will be created in trafodion schema and can be accessed as 
> a regular view.
> This jira will be updated with details on semantics and restrictions
> of creating views on hive tables.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to