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

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

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

    https://github.com/apache/trafodion/pull/1460#discussion_r172066807
  
    --- Diff: core/sql/bin/SqlciErrors.txt ---
    @@ -1331,6 +1331,7 @@ $1~String1 --------------------------------
     4320 ZZZZZ 99999 BEGINNER MAJOR DBADMIN Stream access is not allowed on 
multi-partitioned table or index, when flag ATTEMPT_ASYNCHRONOUS_ACCESS is set 
to OFF. Object in scope: $0~TableName.
     4321 ZZZZZ 99999 BEGINNER MAJOR DBADMIN An embedded update/delete is not 
allowed on a partitioned table, when flag ATTEMPT_ASYNCHRONOUS_ACCESS is set to 
OFF. Object in scope: $0~TableName.
     4322 0A000 99999 BEGINNER MAJOR DBADMIN A column with BLOB datatype cannot 
be used in this clause or function.
    +4323 ZZZZZ 99999 BEGINNER MAJOR DBADMIN Use of predefined UDF $0~String0 
is deprecated and this function will be removed in a future release. Please use 
the function with the same name in schema TRAFODION."_LIBMGR_" instead. You may 
need to issue this command first: INITIALIZE TRAFODION, UPGRADE LIBRARY 
MANAGEMENT.
    --- End diff --
    
    Consider adding this message to the Trafodion Messages Guide.


> Some predefined UDFs should be regular UDFs so we can revoke rights
> -------------------------------------------------------------------
>
>                 Key: TRAFODION-2974
>                 URL: https://issues.apache.org/jira/browse/TRAFODION-2974
>             Project: Apache Trafodion
>          Issue Type: Bug
>          Components: sql-cmu
>    Affects Versions: 2.2.0
>            Reporter: Hans Zeller
>            Assignee: Hans Zeller
>            Priority: Major
>             Fix For: 2.3
>
>
> Roberta pointed out that we have two predefined UDFs, EVENT_LOG_READER and 
> JDBC, where the system administrator should have the ability to control who 
> can execute these functions.
> To do this, these two UDFs cannot be "predefined" UDFs anymore, since those 
> don't have the metadata that's required for doing grant and revoke.
> Roberta also pointed out that the JDBC UDF should refuse to connect to the T2 
> driver, for security reasons.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to