You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Syed S. Albiz (JIRA)" <ji...@apache.org> on 2011/08/03 01:14:27 UTC
[jira] [Created] (HIVE-2335) Indexes are still automatically
queried when out of sync with their source tables
Indexes are still automatically queried when out of sync with their source tables
---------------------------------------------------------------------------------
Key: HIVE-2335
URL: https://issues.apache.org/jira/browse/HIVE-2335
Project: Hive
Issue Type: Bug
Reporter: Syed S. Albiz
The automatic index usage does not check whether or not the indexes are still up-to-date when generating the index queries. This can be addressed in two stages, the first is to add a check before generating the index query to ensure that the index is still valid. The next stage may be to add some sort of mode where indexes are automatically updated on table writes.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2335) Indexes are still automatically
queried when out of sync with their source tables
Posted by "Carl Steinbach (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-2335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carl Steinbach updated HIVE-2335:
---------------------------------
Component/s: Indexing
Fix Version/s: 0.8.0
> Indexes are still automatically queried when out of sync with their source tables
> ---------------------------------------------------------------------------------
>
> Key: HIVE-2335
> URL: https://issues.apache.org/jira/browse/HIVE-2335
> Project: Hive
> Issue Type: Bug
> Components: Indexing
> Reporter: Syed S. Albiz
> Assignee: Syed S. Albiz
> Fix For: 0.8.0
>
> Attachments: HIVE-2335.1.patch, HIVE-2335.2.patch, HIVE-2335.3.patch
>
>
> The automatic index usage does not check whether or not the indexes are still up-to-date when generating the index queries. This can be addressed in two stages, the first is to add a check before generating the index query to ensure that the index is still valid. The next stage may be to add some sort of mode where indexes are automatically updated on table writes.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-2335) Indexes are still automatically
queried when out of sync with their source tables
Posted by "Syed S. Albiz (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-2335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13078495#comment-13078495 ]
Syed S. Albiz commented on HIVE-2335:
-------------------------------------
This change will likely break the change introduced in HIVE-2138, so it will be smoother to have this one get in, and then modify the patch in 2138 to use a more robust testcase to ensure that indexes are actually used
> Indexes are still automatically queried when out of sync with their source tables
> ---------------------------------------------------------------------------------
>
> Key: HIVE-2335
> URL: https://issues.apache.org/jira/browse/HIVE-2335
> Project: Hive
> Issue Type: Bug
> Reporter: Syed S. Albiz
> Assignee: Syed S. Albiz
> Attachments: HIVE-2335.1.patch
>
>
> The automatic index usage does not check whether or not the indexes are still up-to-date when generating the index queries. This can be addressed in two stages, the first is to add a check before generating the index query to ensure that the index is still valid. The next stage may be to add some sort of mode where indexes are automatically updated on table writes.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-2335) Indexes are still automatically
queried when out of sync with their source tables
Posted by "jiraposter@reviews.apache.org (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-2335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13086072#comment-13086072 ]
jiraposter@reviews.apache.org commented on HIVE-2335:
-----------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/1260/
-----------------------------------------------------------
(Updated 2011-08-17 00:57:46.951422)
Review request for hive, John Sichi, Yongqiang He, and Ning Zhang.
Changes
-------
Ning pointed out that there was a race condition with the approach I was using, modified to store the timestamps of the base tables before we kick off the rebuild job.
Summary
-------
Check the timestamps of the tables/partitions to ensure that they were not written to since the index was last generated
This addresses bug HIVE-2335.
https://issues.apache.org/jira/browse/HIVE-2335
Diffs (updated)
-----
ql/src/java/org/apache/hadoop/hive/ql/optimizer/physical/index/IndexWhereProcessor.java 8295687
ql/src/java/org/apache/hadoop/hive/ql/parse/DDLSemanticAnalyzer.java 3054f76
ql/src/java/org/apache/hadoop/hive/ql/plan/AlterIndexDesc.java cf20b89
ql/src/test/queries/clientpositive/index_stale.q PRE-CREATION
ql/src/test/queries/clientpositive/index_stale_partitioned.q PRE-CREATION
ql/src/test/results/clientpositive/index_stale.q.out PRE-CREATION
ql/src/test/results/clientpositive/index_stale_partitioned.q.out PRE-CREATION
Diff: https://reviews.apache.org/r/1260/diff
Testing
-------
added index_stale.q and index_stale_partitioned.q to the testcase suite
Thanks,
Syed
> Indexes are still automatically queried when out of sync with their source tables
> ---------------------------------------------------------------------------------
>
> Key: HIVE-2335
> URL: https://issues.apache.org/jira/browse/HIVE-2335
> Project: Hive
> Issue Type: Bug
> Reporter: Syed S. Albiz
> Assignee: Syed S. Albiz
> Attachments: HIVE-2335.1.patch, HIVE-2335.2.patch
>
>
> The automatic index usage does not check whether or not the indexes are still up-to-date when generating the index queries. This can be addressed in two stages, the first is to add a check before generating the index query to ensure that the index is still valid. The next stage may be to add some sort of mode where indexes are automatically updated on table writes.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2335) Indexes are still automatically
queried when out of sync with their source tables
Posted by "He Yongqiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-2335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
He Yongqiang updated HIVE-2335:
-------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
committed, thanks Syed!
> Indexes are still automatically queried when out of sync with their source tables
> ---------------------------------------------------------------------------------
>
> Key: HIVE-2335
> URL: https://issues.apache.org/jira/browse/HIVE-2335
> Project: Hive
> Issue Type: Bug
> Reporter: Syed S. Albiz
> Assignee: Syed S. Albiz
> Attachments: HIVE-2335.1.patch, HIVE-2335.2.patch, HIVE-2335.3.patch
>
>
> The automatic index usage does not check whether or not the indexes are still up-to-date when generating the index queries. This can be addressed in two stages, the first is to add a check before generating the index query to ensure that the index is still valid. The next stage may be to add some sort of mode where indexes are automatically updated on table writes.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2335) Indexes are still automatically
queried when out of sync with their source tables
Posted by "Syed S. Albiz (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-2335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Syed S. Albiz updated HIVE-2335:
--------------------------------
Attachment: HIVE-2335.3.patch
Forgot to update after HIVE-2286 landed and changed all the indexing testcase outputs
> Indexes are still automatically queried when out of sync with their source tables
> ---------------------------------------------------------------------------------
>
> Key: HIVE-2335
> URL: https://issues.apache.org/jira/browse/HIVE-2335
> Project: Hive
> Issue Type: Bug
> Reporter: Syed S. Albiz
> Assignee: Syed S. Albiz
> Attachments: HIVE-2335.1.patch, HIVE-2335.2.patch, HIVE-2335.3.patch
>
>
> The automatic index usage does not check whether or not the indexes are still up-to-date when generating the index queries. This can be addressed in two stages, the first is to add a check before generating the index query to ensure that the index is still valid. The next stage may be to add some sort of mode where indexes are automatically updated on table writes.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (HIVE-2335) Indexes are still automatically
queried when out of sync with their source tables
Posted by "Syed S. Albiz (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-2335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Syed S. Albiz reassigned HIVE-2335:
-----------------------------------
Assignee: Syed S. Albiz
> Indexes are still automatically queried when out of sync with their source tables
> ---------------------------------------------------------------------------------
>
> Key: HIVE-2335
> URL: https://issues.apache.org/jira/browse/HIVE-2335
> Project: Hive
> Issue Type: Bug
> Reporter: Syed S. Albiz
> Assignee: Syed S. Albiz
>
> The automatic index usage does not check whether or not the indexes are still up-to-date when generating the index queries. This can be addressed in two stages, the first is to add a check before generating the index query to ensure that the index is still valid. The next stage may be to add some sort of mode where indexes are automatically updated on table writes.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2335) Indexes are still automatically
queried when out of sync with their source tables
Posted by "Syed S. Albiz (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-2335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Syed S. Albiz updated HIVE-2335:
--------------------------------
Attachment: HIVE-2335.1.patch
fix + testcases for the immediate solution of checking timestamps to ensure indexes are valid before generating the index queries.
> Indexes are still automatically queried when out of sync with their source tables
> ---------------------------------------------------------------------------------
>
> Key: HIVE-2335
> URL: https://issues.apache.org/jira/browse/HIVE-2335
> Project: Hive
> Issue Type: Bug
> Reporter: Syed S. Albiz
> Assignee: Syed S. Albiz
> Attachments: HIVE-2335.1.patch
>
>
> The automatic index usage does not check whether or not the indexes are still up-to-date when generating the index queries. This can be addressed in two stages, the first is to add a check before generating the index query to ensure that the index is still valid. The next stage may be to add some sort of mode where indexes are automatically updated on table writes.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-2335) Indexes are still automatically
queried when out of sync with their source tables
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-2335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087675#comment-13087675 ]
Hudson commented on HIVE-2335:
------------------------------
Integrated in Hive-trunk-h0.21 #905 (See [https://builds.apache.org/job/Hive-trunk-h0.21/905/])
HIVE-2335: Indexes are still automatically queried when out of sync with their source tables (Syed via He Yongqiang)
heyongqiang : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1159499
Files :
* /hive/trunk/ql/src/test/results/clientpositive/index_stale_partitioned.q.out
* /hive/trunk/ql/src/test/queries/clientpositive/index_stale_partitioned.q
* /hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/parse/DDLSemanticAnalyzer.java
* /hive/trunk/ql/src/test/results/clientpositive/index_stale.q.out
* /hive/trunk/ql/src/test/queries/clientpositive/index_stale.q
* /hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/optimizer/physical/index/IndexWhereProcessor.java
* /hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/plan/AlterIndexDesc.java
> Indexes are still automatically queried when out of sync with their source tables
> ---------------------------------------------------------------------------------
>
> Key: HIVE-2335
> URL: https://issues.apache.org/jira/browse/HIVE-2335
> Project: Hive
> Issue Type: Bug
> Reporter: Syed S. Albiz
> Assignee: Syed S. Albiz
> Attachments: HIVE-2335.1.patch, HIVE-2335.2.patch, HIVE-2335.3.patch
>
>
> The automatic index usage does not check whether or not the indexes are still up-to-date when generating the index queries. This can be addressed in two stages, the first is to add a check before generating the index query to ensure that the index is still valid. The next stage may be to add some sort of mode where indexes are automatically updated on table writes.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-2335) Indexes are still automatically
queried when out of sync with their source tables
Posted by "jiraposter@reviews.apache.org (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-2335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13086927#comment-13086927 ]
jiraposter@reviews.apache.org commented on HIVE-2335:
-----------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/1260/
-----------------------------------------------------------
(Updated 2011-08-18 10:08:30.148104)
Review request for hive, John Sichi, Yongqiang He, and Ning Zhang.
Changes
-------
updated testcases
Summary
-------
Check the timestamps of the tables/partitions to ensure that they were not written to since the index was last generated
This addresses bug HIVE-2335.
https://issues.apache.org/jira/browse/HIVE-2335
Diffs (updated)
-----
ql/src/java/org/apache/hadoop/hive/ql/optimizer/physical/index/IndexWhereProcessor.java 8295687
ql/src/java/org/apache/hadoop/hive/ql/parse/DDLSemanticAnalyzer.java 3054f76
ql/src/java/org/apache/hadoop/hive/ql/plan/AlterIndexDesc.java cf20b89
ql/src/test/queries/clientpositive/index_stale.q PRE-CREATION
ql/src/test/queries/clientpositive/index_stale_partitioned.q PRE-CREATION
ql/src/test/results/clientpositive/index_stale.q.out PRE-CREATION
ql/src/test/results/clientpositive/index_stale_partitioned.q.out PRE-CREATION
Diff: https://reviews.apache.org/r/1260/diff
Testing
-------
added index_stale.q and index_stale_partitioned.q to the testcase suite
Thanks,
Syed
> Indexes are still automatically queried when out of sync with their source tables
> ---------------------------------------------------------------------------------
>
> Key: HIVE-2335
> URL: https://issues.apache.org/jira/browse/HIVE-2335
> Project: Hive
> Issue Type: Bug
> Reporter: Syed S. Albiz
> Assignee: Syed S. Albiz
> Attachments: HIVE-2335.1.patch, HIVE-2335.2.patch, HIVE-2335.3.patch
>
>
> The automatic index usage does not check whether or not the indexes are still up-to-date when generating the index queries. This can be addressed in two stages, the first is to add a check before generating the index query to ensure that the index is still valid. The next stage may be to add some sort of mode where indexes are automatically updated on table writes.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-2335) Indexes are still automatically
queried when out of sync with their source tables
Posted by "He Yongqiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-2335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13086722#comment-13086722 ]
He Yongqiang commented on HIVE-2335:
------------------------------------
+1, looks good.
> Indexes are still automatically queried when out of sync with their source tables
> ---------------------------------------------------------------------------------
>
> Key: HIVE-2335
> URL: https://issues.apache.org/jira/browse/HIVE-2335
> Project: Hive
> Issue Type: Bug
> Reporter: Syed S. Albiz
> Assignee: Syed S. Albiz
> Attachments: HIVE-2335.1.patch, HIVE-2335.2.patch
>
>
> The automatic index usage does not check whether or not the indexes are still up-to-date when generating the index queries. This can be addressed in two stages, the first is to add a check before generating the index query to ensure that the index is still valid. The next stage may be to add some sort of mode where indexes are automatically updated on table writes.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2335) Indexes are still automatically
queried when out of sync with their source tables
Posted by "Syed S. Albiz (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-2335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Syed S. Albiz updated HIVE-2335:
--------------------------------
Attachment: HIVE-2335.2.patch
Ning pointed out that there was a race condition with the approach I was using, modified to store the timestamps of the base tables before we kick off the rebuild job.
> Indexes are still automatically queried when out of sync with their source tables
> ---------------------------------------------------------------------------------
>
> Key: HIVE-2335
> URL: https://issues.apache.org/jira/browse/HIVE-2335
> Project: Hive
> Issue Type: Bug
> Reporter: Syed S. Albiz
> Assignee: Syed S. Albiz
> Attachments: HIVE-2335.1.patch, HIVE-2335.2.patch
>
>
> The automatic index usage does not check whether or not the indexes are still up-to-date when generating the index queries. This can be addressed in two stages, the first is to add a check before generating the index query to ensure that the index is still valid. The next stage may be to add some sort of mode where indexes are automatically updated on table writes.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-2335) Indexes are still automatically
queried when out of sync with their source tables
Posted by "Syed S. Albiz (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-2335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Syed S. Albiz updated HIVE-2335:
--------------------------------
Status: Patch Available (was: Open)
> Indexes are still automatically queried when out of sync with their source tables
> ---------------------------------------------------------------------------------
>
> Key: HIVE-2335
> URL: https://issues.apache.org/jira/browse/HIVE-2335
> Project: Hive
> Issue Type: Bug
> Reporter: Syed S. Albiz
> Assignee: Syed S. Albiz
> Attachments: HIVE-2335.1.patch
>
>
> The automatic index usage does not check whether or not the indexes are still up-to-date when generating the index queries. This can be addressed in two stages, the first is to add a check before generating the index query to ensure that the index is still valid. The next stage may be to add some sort of mode where indexes are automatically updated on table writes.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-2335) Indexes are still automatically
queried when out of sync with their source tables
Posted by "He Yongqiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-2335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087199#comment-13087199 ]
He Yongqiang commented on HIVE-2335:
------------------------------------
+1, running tests
> Indexes are still automatically queried when out of sync with their source tables
> ---------------------------------------------------------------------------------
>
> Key: HIVE-2335
> URL: https://issues.apache.org/jira/browse/HIVE-2335
> Project: Hive
> Issue Type: Bug
> Reporter: Syed S. Albiz
> Assignee: Syed S. Albiz
> Attachments: HIVE-2335.1.patch, HIVE-2335.2.patch, HIVE-2335.3.patch
>
>
> The automatic index usage does not check whether or not the indexes are still up-to-date when generating the index queries. This can be addressed in two stages, the first is to add a check before generating the index query to ensure that the index is still valid. The next stage may be to add some sort of mode where indexes are automatically updated on table writes.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-2335) Indexes are still automatically
queried when out of sync with their source tables
Posted by "jiraposter@reviews.apache.org (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-2335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13078497#comment-13078497 ]
jiraposter@reviews.apache.org commented on HIVE-2335:
-----------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/1260/
-----------------------------------------------------------
Review request for hive, John Sichi, Yongqiang He, and Ning Zhang.
Summary
-------
Check the timestamps of the tables/partitions to ensure that they were not written to since the index was last generated
This addresses bug HIVE-2335.
https://issues.apache.org/jira/browse/HIVE-2335
Diffs
-----
ql/src/java/org/apache/hadoop/hive/ql/optimizer/physical/index/IndexWhereProcessor.java 8295687
ql/src/test/queries/clientpositive/index_stale.q PRE-CREATION
ql/src/test/queries/clientpositive/index_stale_partitioned.q PRE-CREATION
ql/src/test/results/clientpositive/index_stale.q.out PRE-CREATION
ql/src/test/results/clientpositive/index_stale_partitioned.q.out PRE-CREATION
Diff: https://reviews.apache.org/r/1260/diff
Testing
-------
added index_stale.q and index_stale_partitioned.q to the testcase suite
Thanks,
Syed
> Indexes are still automatically queried when out of sync with their source tables
> ---------------------------------------------------------------------------------
>
> Key: HIVE-2335
> URL: https://issues.apache.org/jira/browse/HIVE-2335
> Project: Hive
> Issue Type: Bug
> Reporter: Syed S. Albiz
> Assignee: Syed S. Albiz
> Attachments: HIVE-2335.1.patch
>
>
> The automatic index usage does not check whether or not the indexes are still up-to-date when generating the index queries. This can be addressed in two stages, the first is to add a check before generating the index query to ensure that the index is still valid. The next stage may be to add some sort of mode where indexes are automatically updated on table writes.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-2335) Indexes are still automatically
queried when out of sync with their source tables
Posted by "He Yongqiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-2335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13086844#comment-13086844 ]
He Yongqiang commented on HIVE-2335:
------------------------------------
Can you fix the errors output by the new testcases?
[junit] Begin query: index_stale.q
[junit] Deleted file:/data/users/heyongqiang/hive-trunk-commit/build/ql/test/data/warehouse/temp
[junit] Deleted file:/data/users/heyongqiang/hive-trunk-commit/build/ql/test/data/warehouse/default__temp_temp_index__
[junit] Deleted file:/data/users/heyongqiang/hive-trunk-commit/build/ql/test/data/warehouse/temp
[junit] diff -a -I file: -I pfile: -I hdfs: -I /tmp/ -I invalidscheme: -I lastUpdateTime -I lastAccessTime -I [Oo]wner -I CreateTime -I LastAccessTime -I Location -I LOCATION ' -I transient_lastDdlTime -I last_modified_ -I java.lang.RuntimeException -I at org -I at sun -I at java -I at junit -I Caused by: -I LOCK_QUERYID: -I grantTime -I [.][.][.] [0-9]* more -I USING 'java -cp /data/users/heyongqiang/hive-trunk-commit/build/ql/test/logs/clientpositive/index_stale.q.out /data/users/heyongqiang/hive-trunk-commit/ql/src/test/results/clientpositive/index_stale.q.out
[junit] junit.framework.AssertionFailedError: Client execution results failed with error code = 1
[junit] See build/ql/tmp/hive.log, or try "ant test ... -Dtest.silent=false" to get more logs.
[junit] at junit.framework.Assert.fail(Assert.java:47)
[junit] at org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver_index_stale(TestCliDriver.java:130)
[junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[junit] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[junit] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[junit] at java.lang.reflect.Method.invoke(Method.java:597)
[junit] at junit.framework.TestCase.runTest(TestCase.java:154)
[junit] at junit.framework.TestCase.runBare(TestCase.java:127)
[junit] at junit.framework.TestResult$1.protect(TestResult.java:106)
[junit] at junit.framework.TestResult.runProtected(TestResult.java:124)
[junit] at junit.framework.TestResult.run(TestResult.java:109)
[junit] at junit.framework.TestCase.run(TestCase.java:118)
[junit] at junit.framework.TestSuite.runTest(TestSuite.java:208)
[junit] at junit.framework.TestSuite.run(TestSuite.java:203)
[junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:422)
[junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:931)
[junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:785)
[junit] 29c29
[junit] < PREHOOK: type: ALTERINDEX_REBUILD
[junit] ---
[junit] > PREHOOK: type: QUERY
[junit] 33c33
[junit] < POSTHOOK: type: ALTERINDEX_REBUILD
[junit] ---
[junit] > POSTHOOK: type: QUERY
[junit] Exception: Client execution results failed with error code = 1
[junit] See build/ql/tmp/hive.log, or try "ant test ... -Dtest.silent=false" to get more logs.
[junit] Begin query: index_stale_partitioned.q
[junit] Deleted pfile:/data/users/heyongqiang/hive-trunk-commit/build/ql/test/data/warehouse/temp/foo=bar
[junit] Deleted pfile:/data/users/heyongqiang/hive-trunk-commit/build/ql/test/data/warehouse/default__temp_temp_index__/foo=bar
[junit] Deleted pfile:/data/users/heyongqiang/hive-trunk-commit/build/ql/test/data/warehouse/temp/foo=bar
[junit] diff -a -I file: -I pfile: -I hdfs: -I /tmp/ -I invalidscheme: -I lastUpdateTime -I lastAccessTime -I [Oo]wner -I CreateTime -I LastAccessTime -I Location -I LOCATION ' -I transient_lastDdlTime -I last_modified_ -I java.lang.RuntimeException -I at org -I at sun -I at java -I at junit -I Caused by: -I LOCK_QUERYID: -I grantTime -I [.][.][.] [0-9]* more -I USING 'java -cp /data/users/heyongqiang/hive-trunk-commit/build/ql/test/logs/clientpositive/index_stale_partitioned.q.out /data/users/heyongqiang/hive-trunk-commit/ql/src/test/results/clientpositive/index_stale_partitioned.q.out
[junit] junit.framework.AssertionFailedError: Client execution results failed with error code = 1
[junit] See build/ql/tmp/hive.log, or try "ant test ... -Dtest.silent=false" to get more logs.
[junit] at junit.framework.Assert.fail(Assert.java:47)
[junit] at org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver_index_stale_partitioned(TestCliDriver.java:178)
[junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[junit] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[junit] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[junit] at java.lang.reflect.Method.invoke(Method.java:597)
[junit] at junit.framework.TestCase.runTest(TestCase.java:154)
[junit] at junit.framework.TestCase.runBare(TestCase.java:127)
[junit] at junit.framework.TestResult$1.protect(TestResult.java:106)
[junit] at junit.framework.TestResult.runProtected(TestResult.java:124)
[junit] at junit.framework.TestResult.run(TestResult.java:109)
[junit] at junit.framework.TestCase.run(TestCase.java:118)
[junit] at junit.framework.TestSuite.runTest(TestSuite.java:208)
[junit] at junit.framework.TestSuite.run(TestSuite.java:203)
[junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:422)
[junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:931)
[junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:785)
[junit] 38c38
[junit] < PREHOOK: type: ALTERINDEX_REBUILD
[junit] ---
[junit] > PREHOOK: type: QUERY
[junit] 42c42
[junit] < POSTHOOK: type: ALTERINDEX_REBUILD
[junit] ---
[junit] > POSTHOOK: type: QUERY
> Indexes are still automatically queried when out of sync with their source tables
> ---------------------------------------------------------------------------------
>
> Key: HIVE-2335
> URL: https://issues.apache.org/jira/browse/HIVE-2335
> Project: Hive
> Issue Type: Bug
> Reporter: Syed S. Albiz
> Assignee: Syed S. Albiz
> Attachments: HIVE-2335.1.patch, HIVE-2335.2.patch
>
>
> The automatic index usage does not check whether or not the indexes are still up-to-date when generating the index queries. This can be addressed in two stages, the first is to add a check before generating the index query to ensure that the index is still valid. The next stage may be to add some sort of mode where indexes are automatically updated on table writes.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira