phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-4277) Treat delete markers consistently with puts for point-in-time scans
Date Mon, 23 Oct 2017 20:20:00 GMT

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

Hadoop QA commented on PHOENIX-4277:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12893571/PHOENIX-4277.test.patch
  against master branch at commit 7cdcb2313b08d2eaeb775f0c989642f8d416cfb6.
  ATTACHMENT ID: 12893571

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+0 tests included{color}.  The patch appears to be a documentation, build,
                        or dev patch that doesn't require tests.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:red}-1 lineLengths{color}.  The patch introduces the following lines longer than
100:
    +        setUpTestDriver(new ReadOnlyProps(serverProps.entrySet().iterator()), new ReadOnlyProps(clientProps.entrySet().iterator()));
+    private String[] getArgValues(String schemaName, String dataTable, String indxTable,
Long batchSize,
+    private List<Job> runScrutinyCurrentSCN(String schemaName, String dataTableName,
String indexTableName, Long scrutinyTS) throws Exception {
+        return runScrutiny(getArgValues(schemaName, dataTableName, indexTableName, null,
SourceTable.BOTH, false, null, null, scrutinyTS));

     {color:red}-1 core tests{color}.  The patch failed these unit tests:
     ./phoenix-core/target/failsafe-reports/TEST-org.apache.phoenix.end2end.IndexScrutinyToolIT

Test results: https://builds.apache.org/job/PreCommit-PHOENIX-Build/1566//testReport/
Console output: https://builds.apache.org/job/PreCommit-PHOENIX-Build/1566//console

This message is automatically generated.

> Treat delete markers consistently with puts for point-in-time scans
> -------------------------------------------------------------------
>
>                 Key: PHOENIX-4277
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4277
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: James Taylor
>            Assignee: James Taylor
>             Fix For: 4.13.0
>
>         Attachments: PHOENIX-4277.test.patch, PHOENIX-4277_v2.patch, PHOENIX-4277_v3.patch,
PHOENIX-4277_wip.patch
>
>
> The IndexScrutinyTool relies on doing point-in-time scans to determine consistency between
the index and data tables. Unfortunately, deletes to the tables cause a problem with this
approach, since delete markers take effect even if they're at a later time stamp than the
point-in-time at which the scan is being done (unless KEEP_DELETED_CELLS is true). The logic
of this is that scans should get the same results before and after a compaction take place.
> Taking snapshots does not help with this since they cannot be taken at a point-in-time
and the delete markers will act the same way - there's no way to guarantee that the index
and data table snapshots have the same "logical" set of data.
> Using raw scans would allow us to see the delete markers and do the correct point-in-time
filtering ourselves. We'd need to write the filters to do this correctly (see the Tephra TransactionVisibilityFilter
for an implementation of this that could be adapted). We'd also need to hook this into Phoenix
or potentially dip down to the HBase level  to do this.
> Thanks for brainstorming on this with me, [~lhofhansl].



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message