Jenkins build is unstable: gora-trunk #364
See https://builds.apache.org/job/gora-trunk/364/
Re: Jenkins build is unstable: gora-trunk » Apache Gora :: Cassandra #364
OK so I changed our nightly builds to run on any one of some 5 Ubuntu slaves. This is now failing on only 1 test [0] which is /testQueryWebPageQueryEmptyResults I have actually seen this error before InvalidRequestException(why:start key's md5 sorts after end key's md5. this is not allowed; you probably should not specify end key at all, under RandomPartitioner) Was it intentional to exclude this test from being overriden just now Kaz? From seeing the others (which have been overrideen) I would also expect this one to fall into that category just now. We need to initiate a discussion to find common ground between datastores regarding how Gora treats various query and delete semantics. Thanks have a great weekend Lewis [0] https://builds.apache.org/view/G-L/view/Gora/job/gora-trunk/364/org.apache.gora$gora-cassandra/testReport/org.apache.gora.cassandra.store/TestCassandraStore/testQueryWebPageQueryEmptyResults/ On Sat, Jul 21, 2012 at 12:44 PM, Apache Jenkins Server jenk...@builds.apache.org wrote: See https://builds.apache.org/job/gora-trunk/org.apache.gora$gora-cassandra/364/ -- Lewis
[jira] [Resolved] (GORA-53) Add Gora-Cassandra tests
[ https://issues.apache.org/jira/browse/GORA-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lewis John McGibbney resolved GORA-53. -- Resolution: Fixed Committed @r1362989 in trunk Thanks Kaz for all the hard work. Add Gora-Cassandra tests Key: GORA-53 URL: https://issues.apache.org/jira/browse/GORA-53 Project: Apache Gora Issue Type: Improvement Components: storage-cassandra Affects Versions: 0.1.1-incubating Reporter: Lewis John McGibbney Assignee: Lewis John McGibbney Priority: Critical Fix For: 0.3 Attachments: GORA-53-final.patch, GORA-53-v2.patch, GORA-53.patch, GORA-54-v8.patch, GORA-test.patch, test.txt As per this thread [1], it is absolutely essential that we get some tests for the Cassandra module. Therefore this task should act as a summary task to manage all test which are hereby proposed. Realistically, this is going to take a good while, so I have marked it for 0.2 and 0.3-incubating releases. [1] http://www.mail-archive.com/gora-dev@incubator.apache.org/msg00241.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GORA-158) Improve error logging when gora-$module-mapping.xml is not correctly defined
Lewis John McGibbney created GORA-158:
-
Summary: Improve error logging when gora-$module-mapping.xml is
not correctly defined
Key: GORA-158
URL: https://issues.apache.org/jira/browse/GORA-158
Project: Apache Gora
Issue Type: Bug
Components: storage
Affects Versions: 0.2
Reporter: Lewis John McGibbney
Fix For: 0.3
I've recently encountered this myself during running gora-cassandra aginst
Keith Turner's goraci module where my gora-cassandra-mapping.xml configuration
was incorrect. This has also been experienced further downstream in Nutch 2.X
land where new users are met with a rather hellish stack such as the following
{code}
12/07/21 13:04:27 INFO mapred.JobClient: Task Id :
attempt_201207211239_0003_m_01_2, Status : FAILED
org.apache.gora.util.GoraException: java.io.IOException
at
org.apache.gora.store.DataStoreFactory.createDataStore(DataStoreFactory.java:167)
at
org.apache.gora.store.DataStoreFactory.getDataStore(DataStoreFactory.java:278)
at goraci.Generator$GeneratorMapper.map(Generator.java:197)
at goraci.Generator$GeneratorMapper.map(Generator.java:179)
at org.apache.hadoop.mapreduce.Mapper.run(Mapper.java:144)
at org.apache.hadoop.mapred.MapTask.runNewMapper(MapTask.java:764)
at org.apache.hadoop.mapred.MapTask.run(MapTask.java:370)
at org.apache.hadoop.mapred.Child$4.run(Child.java:255)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:396)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1093)
at org.apache.hadoop.mapred.Child.main(Child.java:249)
Caused by: java.io.IOException
at
org.apache.gora.cassandra.store.CassandraStore.initialize(CassandraStore.java:88)
at
org.apache.gora.store.DataStoreFactory.initializeDataStore(DataStoreFactory.java:102)
at
org.apache.gora.store.DataStoreFactory.createDataStore(DataStoreFactory.java:161)
... 11 more
Caused by: java.lang.NullPointerException
at
org.apache.gora.cassandra.store.CassandraMapping.init(CassandraMapping.java:117)
at
org.apache.gora.cassandra.store.CassandraMappingManager.get(CassandraMappingManager.java:84)
at
org.apache.gora.cassandra.store.CassandraClient.initialize(CassandraClient.java:83)
at
org.apache.gora.cassandra.store.CassandraStore.initialize(CassandraStore.java:85)
... 13 more
{code}
We should implement much better logging for this which clearly specifies that
it is a mapping problem due to incorrect mapping configuration.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Jenkins build is unstable: gora-trunk » Apache Gora :: Cassandra #364
It is because cassandra.yaml has: partitioner: org.apache.cassandra.dht.RandomPartitioner For key range query, it must be changed to: partitioner: org.apache.cassandra.dht.ByteOrderedPartitioner I will be fixing it shortly. -Kaz On 7/21/12 4:52 AM, Lewis John Mcgibbney wrote: OK so I changed our nightly builds to run on any one of some 5 Ubuntu slaves. This is now failing on only 1 test [0] which is /testQueryWebPageQueryEmptyResults I have actually seen this error before InvalidRequestException(why:start key's md5 sorts after end key's md5. this is not allowed; you probably should not specify end key at all, under RandomPartitioner) Was it intentional to exclude this test from being overriden just now Kaz? From seeing the others (which have been overrideen) I would also expect this one to fall into that category just now. We need to initiate a discussion to find common ground between datastores regarding how Gora treats various query and delete semantics. Thanks have a great weekend Lewis [0] https://builds.apache.org/view/G-L/view/Gora/job/gora-trunk/364/org.apache.gora$gora-cassandra/testReport/org.apache.gora.cassandra.store/TestCassandraStore/testQueryWebPageQueryEmptyResults/ On Sat, Jul 21, 2012 at 12:44 PM, Apache Jenkins Server jenk...@builds.apache.org wrote: See https://builds.apache.org/job/gora-trunk/org.apache.gora$gora-cassandra/364/
Re: Jenkins build is unstable: gora-trunk » Apache Gora :: Cassandra #364
OK Kaz Please revert my commit as you see fit. Thank you Lewis Out of curiosity, I wonder if you've run gora-cassandra against Keith Turner's goraci test suite[0]? I'm currently bringing the cassandra config up to date and will send him a pull request shortly. [0] https://github.com/keith-turner/goraci/ On Sat, Jul 21, 2012 at 1:36 PM, Kazuomi Kashii kazu...@kashii.net wrote: It is because cassandra.yaml has: partitioner: org.apache.cassandra.dht.RandomPartitioner For key range query, it must be changed to: partitioner: org.apache.cassandra.dht.ByteOrderedPartitioner I will be fixing it shortly. -Kaz On 7/21/12 4:52 AM, Lewis John Mcgibbney wrote: OK so I changed our nightly builds to run on any one of some 5 Ubuntu slaves. This is now failing on only 1 test [0] which is /testQueryWebPageQueryEmptyResults I have actually seen this error before InvalidRequestException(why:start key's md5 sorts after end key's md5. this is not allowed; you probably should not specify end key at all, under RandomPartitioner) Was it intentional to exclude this test from being overriden just now Kaz? From seeing the others (which have been overrideen) I would also expect this one to fall into that category just now. We need to initiate a discussion to find common ground between datastores regarding how Gora treats various query and delete semantics. Thanks have a great weekend Lewis [0] https://builds.apache.org/view/G-L/view/Gora/job/gora-trunk/364/org.apache.gora$gora-cassandra/testReport/org.apache.gora.cassandra.store/TestCassandraStore/testQueryWebPageQueryEmptyResults/ On Sat, Jul 21, 2012 at 12:44 PM, Apache Jenkins Server jenk...@builds.apache.org wrote: See https://builds.apache.org/job/gora-trunk/org.apache.gora$gora-cassandra/364/ -- Lewis
[jira] [Updated] (GORA-157) gora-cassandra test failure - proposal to skip 10 test cases for a while
[ https://issues.apache.org/jira/browse/GORA-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kazuomi Kashii updated GORA-157: Attachment: GORA-157-v2.patch To fix the following error: testQueryWebPageQueryEmptyResults(org.apache.gora.cassandra.store.TestCassandraStore): InvalidRequestException(why:start key's md5 sorts after end key's md5. this is not allowed; you probably should not specify end key at all, under RandomPartitioner) ByteOrderedPartitioner is required for key range query. gora-cassandra test failure - proposal to skip 10 test cases for a while Key: GORA-157 URL: https://issues.apache.org/jira/browse/GORA-157 Project: Apache Gora Issue Type: Test Components: testing Affects Versions: 0.3 Reporter: Kazuomi Kashii Attachments: GORA-157-v2.patch, GORA-157.patch gora-cassandra test has failed since GORA-53-final.patch was committed. Even though some issues such as GORA-151, 152, and 153 have been fixed, there are still 10 failures. I'd propose to skil these 10 test cases at TestCassandraStore.java like TestHBaseStore.java. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GORA-157) gora-cassandra test failure - proposal to skip 10 test cases for a while
[ https://issues.apache.org/jira/browse/GORA-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419819#comment-13419819 ] Kazuomi Kashii commented on GORA-157: - $ svn commit --username kazk --message Fixes GORA-157 testQueryWebPageQueryEmptyResults by using ByteOrderedPartitioner instead of RandomPartitioner Sendinggora-cassandra/src/test/conf/cassandra.yaml Transmitting file data . Committed revision 1364074. $ gora-cassandra test failure - proposal to skip 10 test cases for a while Key: GORA-157 URL: https://issues.apache.org/jira/browse/GORA-157 Project: Apache Gora Issue Type: Test Components: testing Affects Versions: 0.3 Reporter: Kazuomi Kashii Attachments: GORA-157-v2.patch, GORA-157.patch gora-cassandra test has failed since GORA-53-final.patch was committed. Even though some issues such as GORA-151, 152, and 153 have been fixed, there are still 10 failures. I'd propose to skil these 10 test cases at TestCassandraStore.java like TestHBaseStore.java. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
Jenkins build is still unstable: gora-trunk » Apache Gora :: Cassandra #365
See https://builds.apache.org/job/gora-trunk/org.apache.gora$gora-cassandra/changes
Jenkins build is still unstable: gora-trunk #365
See https://builds.apache.org/job/gora-trunk/changes
Build failed in Jenkins: gora-trunk #366
See https://builds.apache.org/job/gora-trunk/366/changes Changes: [lewismc] revert commit to disable testQueryWebPageQueryEmptyResults -- [...truncated 197 lines...] AUgora-accumulo/src/test/resources/gora-accumulo-mapping.xml A gora-accumulo/src/main A gora-accumulo/src/main/java A gora-accumulo/src/main/java/org A gora-accumulo/src/main/java/org/apache A gora-accumulo/src/main/java/org/apache/gora A gora-accumulo/src/main/java/org/apache/gora/accumulo A gora-accumulo/src/main/java/org/apache/gora/accumulo/encoders AU gora-accumulo/src/main/java/org/apache/gora/accumulo/encoders/Encoder.java AU gora-accumulo/src/main/java/org/apache/gora/accumulo/encoders/Utils.java AU gora-accumulo/src/main/java/org/apache/gora/accumulo/encoders/BinaryEncoder.java AU gora-accumulo/src/main/java/org/apache/gora/accumulo/encoders/HexEncoder.java AU gora-accumulo/src/main/java/org/apache/gora/accumulo/encoders/SignedBinaryEncoder.java A gora-accumulo/src/main/java/org/apache/gora/accumulo/query AU gora-accumulo/src/main/java/org/apache/gora/accumulo/query/AccumuloResult.java AU gora-accumulo/src/main/java/org/apache/gora/accumulo/query/AccumuloQuery.java A gora-accumulo/src/main/java/org/apache/gora/accumulo/store AU gora-accumulo/src/main/java/org/apache/gora/accumulo/store/AccumuloMapping.java AU gora-accumulo/src/main/java/org/apache/gora/accumulo/store/AccumuloStore.java A gora-accumulo/src/main/java/org/apache/gora/accumulo/util AU gora-accumulo/src/main/java/org/apache/gora/accumulo/util/FixedByteArrayOutputStream.java A gora-accumulo/src/examples A gora-accumulo/src/examples/java A gora-accumulo/src/examples/java/.gitignore AUgora-accumulo/pom.xml AUNOTICE.txt AULICENSE.txt A .gitignore A doap_Gora.rdf A ivy AUivy/ivysettings.xml AUivy/ivy-2.1.0.jar AUivy/ivy-configurations.xml A gora-hbase A gora-hbase/lib-ext A gora-hbase/lib-ext/.gitignore A gora-hbase/conf A gora-hbase/conf/.gitignore A gora-hbase/ivy AUgora-hbase/ivy/ivy.xml A gora-hbase/src A gora-hbase/src/test A gora-hbase/src/test/java A gora-hbase/src/test/java/org A gora-hbase/src/test/java/org/apache A gora-hbase/src/test/java/org/apache/gora A gora-hbase/src/test/java/org/apache/gora/hbase A gora-hbase/src/test/java/org/apache/gora/hbase/mapreduce AU gora-hbase/src/test/java/org/apache/gora/hbase/mapreduce/TestHBaseStoreWordCount.java AU gora-hbase/src/test/java/org/apache/gora/hbase/mapreduce/TestHBaseStoreCountQuery.java AU gora-hbase/src/test/java/org/apache/gora/hbase/GoraHBaseTestDriver.java A gora-hbase/src/test/java/org/apache/gora/hbase/store AU gora-hbase/src/test/java/org/apache/gora/hbase/store/TestHBaseStore.java A gora-hbase/src/test/java/org/apache/gora/hbase/util AU gora-hbase/src/test/java/org/apache/gora/hbase/util/TestHBaseByteInterface.java A gora-hbase/src/test/conf AUgora-hbase/src/test/conf/gora-hbase-mapping.xml AUgora-hbase/src/test/conf/hbase-site.xml A gora-hbase/src/main A gora-hbase/src/main/java A gora-hbase/src/main/java/org A gora-hbase/src/main/java/org/apache A gora-hbase/src/main/java/org/apache/gora A gora-hbase/src/main/java/org/apache/gora/hbase A gora-hbase/src/main/java/org/apache/gora/hbase/query AU gora-hbase/src/main/java/org/apache/gora/hbase/query/HBaseGetResult.java AUgora-hbase/src/main/java/org/apache/gora/hbase/query/HBaseResult.java AUgora-hbase/src/main/java/org/apache/gora/hbase/query/HBaseQuery.java AU gora-hbase/src/main/java/org/apache/gora/hbase/query/HBaseScannerResult.java A gora-hbase/src/main/java/org/apache/gora/hbase/store AUgora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseStore.java AUgora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseColumn.java A gora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseTableConnection.java AUgora-hbase/src/main/java/org/apache/gora/hbase/store/HBaseMapping.java A gora-hbase/src/main/java/org/apache/gora/hbase/util AU gora-hbase/src/main/java/org/apache/gora/hbase/util/HBaseByteInterface.java A gora-hbase/src/examples A gora-hbase/src/examples/java A gora-hbase/src/examples/java/.gitignore A gora-hbase/pom.xml AUgora-hbase/build.xml A bin AUbin/gora AUbin/compile-examples.sh AUREADME.txt AUKEYS A gora-core A gora-core/lib-ext A gora-core/lib-ext/.gitignore A gora-core/conf A
Jenkins build is back to normal : gora-trunk #367
See https://builds.apache.org/job/gora-trunk/367/
[jira] [Created] (GORA-159) gora-hbase MR tests should use HBaseTestingUtility instead of deprecated HBaseClusterTestCase
Lewis John McGibbney created GORA-159: - Summary: gora-hbase MR tests should use HBaseTestingUtility instead of deprecated HBaseClusterTestCase Key: GORA-159 URL: https://issues.apache.org/jira/browse/GORA-159 Project: Apache Gora Issue Type: Improvement Components: storage-hbase Affects Versions: 0.2 Reporter: Lewis John McGibbney Fix For: 0.3 I don't know when, but the HBaseClusterTestCase we are currently using in the hbase tests has been deprecated for some time now. I think as part of improving both the execution of gora-* test cases we should aim to keep this stuff up-to-date. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
Jenkins build is back to stable : goraamazon_branch » Apache Gora :: Hbase #23
See https://builds.apache.org/job/goraamazon_branch/org.apache.gora$gora-hbase/23/
Jenkins build is back to stable : goraamazon_branch #23
See https://builds.apache.org/job/goraamazon_branch/23/
