Daniel Wong created PHOENIX-5663:
------------------------------------

             Summary: Phoenix Column Result Size should adhere to Schema
                 Key: PHOENIX-5663
                 URL: https://issues.apache.org/jira/browse/PHOENIX-5663
             Project: Phoenix
          Issue Type: Improvement
    Affects Versions: 4.14.3
            Reporter: Daniel Wong


I found an issue where HBase was used to modify data in a Phoenix table where a 
select statement returned VARCHAR was longer than the schema defined VARCHAR.  
This could occur for example if we made a Phoenix table over an existing HBase 
table.  On first inspection it seems bad for the end user to have to check a 
result for length after it was defined with a max length. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to