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

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

{noformat}
commit c97592b7173e2d6625a50a9a936999a0a3fb3dd5 (HEAD -> master, origin/master, 
origin/HEAD)
Author: Radhika Kundam <radhika.kun...@gmail.com>
Date:   Tue Oct 29 13:04:57 2024 -0700

    RANGER-4975: DB patch fix to support for new columns in Ranger Dataset for 
MySql and Postrgres

    Signed-off-by: Madhan Neethiraj <mad...@apache.org>
 {noformat}

> DB patch fix to support for new columns in Ranger Dataset for MySql and 
> Postrgres
> ---------------------------------------------------------------------------------
>
>                 Key: RANGER-4975
>                 URL: https://issues.apache.org/jira/browse/RANGER-4975
>             Project: Ranger
>          Issue Type: Bug
>          Components: Ranger
>            Reporter: Radhika Kundam
>            Assignee: Radhika Kundam
>            Priority: Major
>             Fix For: 3.0.0
>
>
> Fix for RANGER-4933 introduced changes in DB patches to add new columns 
> ({{{}validity_schedule{}}}, {{{}labels{}}}, {{{}keywords{}}}) to the DataSet 
> table. These new columns need to be included in the core_db SQL script to 
> ensure they are reflected during Ranger schema creation.



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

Reply via email to