[
https://issues.apache.org/jira/browse/DRILL-4425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15167510#comment-15167510
]
Jason Altekruse commented on DRILL-4425:
----------------------------------------
I think that makes a lot of sense. Something like hbase_empty_col_name, or I
guess if this is possible to be found in other systems we shouldn't include the
source in the name. We can make it configurable, just in case someone manages
to collide with whatever we pick.
So I guess we would need to add this to the schema registration of sources, as
well as the record readers that will actually grab data from the source, and we
would assume that only the sentinel would appear in the rest of planning and
execution?
> Handle blank column names in Hbase in CONVERT_FROM
> --------------------------------------------------
>
> Key: DRILL-4425
> URL: https://issues.apache.org/jira/browse/DRILL-4425
> Project: Apache Drill
> Issue Type: New Feature
> Components: Storage - HBase
> Affects Versions: 1.3.0
> Environment: Apache Drill 1.3 on HortonWorks HDP VM 2.1
> Reporter: Saurabh Nigam
> Labels: easyfix
>
> Hbase table may contain blank column names & blank column family names. Drill
> needs to handle such situation.
> I faced the issue when I had a column with blank column name in my Hbase
> Table. To reproduce it :
> -Create a column without any name in Hbase
> -Try to access it via Drill console
> -Try to use CONVERT_FROM function to convert that data from Base64 encoding
> to make it readable. You wont be able to convert blank column because you
> cannot use blank in your query after a dot.
> Something like this
> SELECT CONVERT_FROM(students. , 'UTF8') AS zipcode
> FROM students;
> Where column name is blank
> We need to provide a placeholder for blank column names
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
