Cassandra Keyspace TableName Tools Handling

Cassandra Keyspace TableName Tools Handling

If you create a keyspace named "abc" then pass in a keyspace-prefixed table name to the tools you can't export:
$ bin/geomesa-cassandra ingest -k abc -c abc.foobar -s twitter -C twitter -P 127.0.0.1:9042 ~/20170101-002439.txt.gz
this ingests fine according to the tools...but after this you can't export anything...but its there...kinda
[ec2-user@ip-172-30-2-223 geomesa-cassandra_2.11-1.3.1-SNAPSHOT]$ bin/geomesa-cassandra export -m 1 -k abc -c foobar -f twitter -P 127.0.0.1:9042 id,user_id:String:index=true,user_name:String,text:String,in_reply_to_user_id:String,in_reply_to_status_id:String,hashtags:String,media:String,symbols:String,urls:String,user_mentions:String,retweet_count:Integer,lang:String,place_name:String,place_type:String,place_country_code:String,place_full_name:String,place_id:String,dtg:Date,*geom:Point:srid=4326 [ec2-user@ip-172-30-2-223 geomesa-cassandra_2.11-1.3.1-SNAPSHOT]$ bin/geomesa-cassandra export -m 1 -k abc -c abc.foobar -f twitter -P 127.0.0.1:9042 ERROR Schema 'twitter' has not been initialized. Please call 'createSchema' first.
if you don't use the keyspace prefix on -c it works:
$ bin/geomesa-cassandra ingest -k newone -c foobar -s twitter -C twitter -P 127.0.0.1:9042 ~/20170101-002439.txt.gz $ bin/geomesa-cassandra export -m 1 -k newone -c foobar -f twitter -P 127.0.0.1:9042
Should add some checks or something and not successfully ingest.

Original JIRA Issue: https://geomesa.atlassian.net/browse/GEOMESA-1715

Key: GEOMESA-1715
Type: Improvement
Priority: Minor
Status: To Do
Resolution: Unresolved
Reporter: Andrew Hulbert
Created: Wed, 8 Mar 2017 15:43:15 -0500
Updated: Thu, 1 Jun 2017 14:02:18 -0400
Affects Version(s): 1.3.1
Component(s): Cassandra

Start with the bin/geomesa-cassandra ingest and export commands and reproduce the provided keyspace-prefixed and unprefixed table-name cases against Cassandra. Trace how the tools handle -k and -c, then verify that an invalid prefixed name is rejected instead of reporting successful ingestion, while the valid unprefixed workflow still works.