hbase-issues mailing list archives

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

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

Ted Yu commented on HBASE-14406:
--------------------------------

Based on patch v6:
{code}
HBaseContextSuite:
*** RUN ABORTED ***
  java.io.IOException: Unable to determine a plan to assign region(s)
  at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
  at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
  at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
  at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
  at org.apache.hadoop.ipc.RemoteException.instantiateException(RemoteException.java:106)
  at org.apache.hadoop.ipc.RemoteException.unwrapRemoteException(RemoteException.java:95)
  at org.apache.hadoop.hbase.util.ForeignExceptionUtil.toIOException(ForeignExceptionUtil.java:45)
  at org.apache.hadoop.hbase.client.HBaseAdmin$ProcedureFuture.convertResult(HBaseAdmin.java:4513)
  at org.apache.hadoop.hbase.client.HBaseAdmin$ProcedureFuture.waitProcedureResult(HBaseAdmin.java:4471)
  at org.apache.hadoop.hbase.client.HBaseAdmin$ProcedureFuture.get(HBaseAdmin.java:4405)
  ...
  Cause: org.apache.hadoop.ipc.RemoteException: Unable to determine a plan to assign region(s)
  at org.apache.hadoop.hbase.master.AssignmentManager.assign(AssignmentManager.java:1497)
  at org.apache.hadoop.hbase.util.ModifyRegionUtils.assignRegions(ModifyRegionUtils.java:254)
  at org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.assignRegions(CreateTableProcedure.java:430)
  at org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.executeFromState(CreateTableProcedure.java:126)
  at org.apache.hadoop.hbase.master.procedure.CreateTableProcedure.executeFromState(CreateTableProcedure.java:57)
  at org.apache.hadoop.hbase.procedure2.StateMachineProcedure.execute(StateMachineProcedure.java:119)
  at org.apache.hadoop.hbase.procedure2.Procedure.doExecute(Procedure.java:442)
  at org.apache.hadoop.hbase.procedure2.ProcedureExecutor.execProcedure(ProcedureExecutor.java:1002)
  at org.apache.hadoop.hbase.procedure2.ProcedureExecutor.execLoop(ProcedureExecutor.java:793)
  at org.apache.hadoop.hbase.procedure2.ProcedureExecutor.execLoop(ProcedureExecutor.java:746)
{code}

> The dataframe datasource filter is wrong, and will result in data loss or unexpected
behavior
> ---------------------------------------------------------------------------------------------
>
>                 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
>
>
> 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
(v6.3.4#6332)

Mime
View raw message