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

Kazuomi Kashii edited comment on GORA-53 at 7/12/12 3:56 PM:
-------------------------------------------------------------

It is because of  InvalidRequestException(why:Cannot drop non existing keyspace 
'Employee'.) 
at 
org.apache.gora.cassandra.store.CassandraClient.dropKeyspace(CassandraClient.java:128)
 

    try {
      this.cluster.dropKeyspace(this.cassandraMapping.getKeyspaceName());
    }
    catch (Exception e) {
      LOG.info(e.toString());
    }

would fix them (we may want better exception handling..), but we see another 
ones.

Tests run: 28, Failures: 0, Errors: 27, Skipped: 0, Time elapsed: 2.076 sec <<< 
FAILURE!
testCreateSchema(org.apache.gora.cassandra.store.TestCassandraStore)  Time 
elapsed: 0.002 sec  <<< ERROR!
java.lang.NullPointerException
        at 
org.apache.gora.store.DataStoreTestUtil.testCreateEmployeeSchema(DataStoreTestUtil.java:102)
        at 
org.apache.gora.store.DataStoreTestBase.testCreateSchema(DataStoreTestBase.java:129)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
...

It seems that dataset has not been set (or not passed) at the following method.

  public static void testCreateEmployeeSchema(DataStore<String, Employee> 
dataStore)
  throws IOException {
    dataStore.createSchema();

    //should not throw exception
    dataStore.createSchema();
  }

It is called by DataStoreTestBase:

  @Test
  public void testCreateSchema() throws Exception {
    log.info("test method: testCreateSchema");
    DataStoreTestUtil.testCreateEmployeeSchema(employeeStore);
    assertSchemaExists("Employee");
  }

so employeeStore has not been set before that.

                
      was (Author: kazk):
    It is because of  InvalidRequestException(why:Cannot drop non existing 
keyspace 'Employee'.) 
at 
org.apache.gora.cassandra.store.CassandraClient.dropKeyspace(CassandraClient.java:128)
 

    try {
      this.cluster.dropKeyspace(this.cassandraMapping.getKeyspaceName());
    }
    catch (Exception e) {
      LOG.info(e.toString());
    }

would fix them (we may want better exception handling..), but we see another 
ones.

Tests run: 28, Failures: 0, Errors: 27, Skipped: 0, Time elapsed: 2.076 sec <<< 
FAILURE!
testCreateSchema(org.apache.gora.cassandra.store.TestCassandraStore)  Time 
elapsed: 0.002 sec  <<< ERROR!
java.lang.NullPointerException
        at 
org.apache.gora.store.DataStoreTestUtil.testCreateEmployeeSchema(DataStoreTestUtil.java:102)
        at 
org.apache.gora.store.DataStoreTestBase.testCreateSchema(DataStoreTestBase.java:129)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
...

It seems that dataset is not set (or not passed) at the following.

  public static void testCreateEmployeeSchema(DataStore<String, Employee> 
dataStore)
  throws IOException {
    dataStore.createSchema();

    //should not throw exception
    dataStore.createSchema();
  }



                  
> 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-v2.patch, GORA-53.patch, GORA-54-v8.patch
>
>
> 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

        

Reply via email to