[
https://issues.apache.org/jira/browse/HIVE-26230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on HIVE-26230 started by Ádám Szita.
-----------------------------------------
> Option to URL encode special chars in hbase.column.mapping that are valid
> HBase column family chars
> ---------------------------------------------------------------------------------------------------
>
> Key: HIVE-26230
> URL: https://issues.apache.org/jira/browse/HIVE-26230
> Project: Hive
> Issue Type: Improvement
> Reporter: Ádám Szita
> Assignee: Ádám Szita
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> HIVE-26015 and HIVE-26139 aimed to fix a missing special character handling
> of values provided for hbase.column.mapping. Values here are used as an URL
> for Ranger based authentication and special characters need to be URL encoded
> for this feature.
> This is currently done only for # char. We should handle all special
> characters that are valid HBase column family characters but count as special
> characters for URLs.
> The URL encoding of HIVE-26015 should come back, as in HBase we can have
> almost any characters for column family (excluding : / ). To make this a
> backward-compatible change, the URL encoding will essentially be optional, so
> users won't have to make changes to their working environment. Should they
> encounter a special character in their HBase table definition though, they
> can turn this URL encoding feature on, which in turn comes with the
> requirement from their end to update their Ranger policies so they are in URL
> encoded format for these tables.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
