[ 
https://issues.apache.org/jira/browse/PHOENIX-63?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13984921#comment-13984921
 ] 

James Taylor commented on PHOENIX-63:
-------------------------------------

I'm getting the following errors when trying to apply the patch to the 3.0 
branch:
PHOENIX63_v1.patch:50: space before tab in indent.
        Properties props = new Properties(TEST_PROPERTIES);
PHOENIX63_v1.patch:51: space before tab in indent.
        Connection conn = DriverManager.getConnection(getUrl(), props);
PHOENIX63_v1.patch:52: space before tab in indent.
        conn.setAutoCommit(false);
PHOENIX63_v1.patch:53: space before tab in indent.
        try {
PHOENIX63_v1.patch:54: space before tab in indent.
                Statement stmt = conn.createStatement();
error: patch failed: 
phoenix-core/src/main/java/org/apache/phoenix/index/IndexMaintainer.java:34
error: 
phoenix-core/src/main/java/org/apache/phoenix/index/IndexMaintainer.java: patch 
does not apply


> Can't add null value to a secondary indexed table
> -------------------------------------------------
>
>                 Key: PHOENIX-63
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-63
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 2.2.3, 3.0.0, 4.0.0, 5.0.0
>            Reporter: job thomas
>            Assignee: Samarth Jain
>         Attachments: PHOENIX63_v1.patch
>
>
> I have  created a Phoenix table like this 
> CREATE TABLE DEMO(R VARCHAR PRIMARY KEY,A DOUBLE,C VARCHAR);
> Then created index 
> CREATE INDEX DEMO_idx ON DEMO (A) INCLUDE(C);
> upsert into DEMO  values('cc1',null,'abc');
> select * from DEMO;
> No Data Found !!
>  
> Problem is when adding null value to the second column(A) 
>  
> If a created  index without include key
> CREATE INDEX DEMO_idx ON DEMO (A) ;
>                       (OR)
> CREATE INDEX DEMO_idx ON DEMO (A,C);
>  
> The same will work properly.
>  
> What will be the reason with include and null value insert?



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to