You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Madhan Neethiraj (Jira)" <ji...@apache.org> on 2022/12/02 07:31:00 UTC

[jira] [Resolved] (RANGER-3983) Support getColumnMasks and getRowFilters in Trino SPI 376+

     [ https://issues.apache.org/jira/browse/RANGER-3983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Madhan Neethiraj resolved RANGER-3983.
--------------------------------------
    Fix Version/s: 3.0.0
                   2.4.0
       Resolution: Fixed

[~ttzztztz] - thank you for the patch. It is now merged in master and ranger-2.4 branches.

 
{noformat}
commit 97137609e14342a3db2112be27c0e809b261e782 (HEAD -> master, origin/master, origin/HEAD)
Author: Ziyue Yang <ya...@outlook.com>
Date:   Thu Dec 1 22:49:32 2022 -0800

    RANGER-3983: Support getColumnMasks and getRowFilters in Trino SPI 376+

    Signed-off-by: Madhan Neethiraj <ma...@apache.org>
{noformat}
 
{noformat}
commit 69895d30a5047c940ca5117427e2ca36475b2ba2 (HEAD -> ranger-2.4, origin/ranger-2.4)
Author: Ziyue Yang <ya...@outlook.com>
Date:   Thu Dec 1 22:49:32 2022 -0800

    RANGER-3983: Support getColumnMasks and getRowFilters in Trino SPI 376+

    Signed-off-by: Madhan Neethiraj <ma...@apache.org>
    (cherry picked from commit 97137609e14342a3db2112be27c0e809b261e782)
{noformat}

> Support getColumnMasks and getRowFilters in Trino SPI 376+
> ----------------------------------------------------------
>
>                 Key: RANGER-3983
>                 URL: https://issues.apache.org/jira/browse/RANGER-3983
>             Project: Ranger
>          Issue Type: Improvement
>          Components: plugins
>            Reporter: ziyue
>            Priority: Major
>             Fix For: 3.0.0, 2.4.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> [https://github.com/trinodb/trino/commit/827de57a50426e804761044d24d96b8877b62b7e]
>  
> The functions `getColumnMask` and `getRowFilter` were deprecated since trino 376, and were removed in 401.
>  
> So we should adapt to that change in ranger implementation



--
This message was sent by Atlassian Jira
(v8.20.10#820010)