hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Malaska (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-14406) The dataframe datasource filter is wrong, and will result in data loss or unexpected behavior
Date Thu, 15 Oct 2015 21:04:05 GMT

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

Ted Malaska updated HBASE-14406:
    Attachment: HBASE-14406.9.patch

rebasing pom.

On a side note something funky happen to hbase when I rebased.  On my computer all the unit
tests are broken in the master branch unless I do a "reverse look-up-able IP" to make it work.
 This issue is unrelated to my patch it was something else that change recently.

I get this error 
java.io.IOException: java.lang.RuntimeException: Could not resolve Kerberos principal name:
java.net.UnknownHostException: tmalaska-MBP-2.home: tmalaska-MBP-2.home: nodename nor servname
provided, or not known

On a HBaseTestingUtility startMiniCluster

I have tested this on more then one computer with friends.  

So repeat the patch should be good, but something is not good with HBase in the latest master
with respeck to HBaseTestingUtility startMiniCluster

> The dataframe datasource filter is wrong, and will result in data loss or unexpected
> ---------------------------------------------------------------------------------------------
>                 Key: HBASE-14406
>                 URL: https://issues.apache.org/jira/browse/HBASE-14406
>             Project: HBase
>          Issue Type: Bug
>          Components: spark
>    Affects Versions: 2.0.0
>            Reporter: Zhan Zhang
>            Assignee: Ted Malaska
>            Priority: Blocker
>             Fix For: 2.0.0
>         Attachments: HBASE-14406.1.patch, HBASE-14406.2.patch, HBASE-14406.3.patch, HBASE-14406.4.patch,
HBASE-14406.5.patch, HBASE-14406.6.patch, HBASE-14406.7.patch, HBASE-14406.9.patch, Surefile-reports.zip
> Following condition will result in the same filter. It will have data loss with the current
filter construction.
> col1 > 4 && col2 < 3
> col1 > 4 || col2 < 3

This message was sent by Atlassian JIRA

View raw message