Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [geomesa-users] was location added as a new reserved word in geomesa 1.2.4 and beyond?

Emilio,

 

Thanks, I’ll try that override shortly I hope. 

 

Yes I was ingesting new with same data and same schema but to a whole new catalog name because there may be another issue happening to us.  I’m trying to determine if I can reproduce another issue.  Short term I just renamed the field in my test schemas to get around this as I do not think that is the problem but I’ll keep it in mind in case I can’t recreate.

 

So thanks for that workaround! We will certainly consider if we should continue to use something that is a reserved word. 

 

Thanks!

Diane

From: geomesa-users-bounces@xxxxxxxxxxxxxxxx [mailto:geomesa-users-bounces@xxxxxxxxxxxxxxxx] On Behalf Of Emilio Lahr-Vivaz
Sent: Tuesday, September 06, 2016 3:26 PM
To: geomesa-users@xxxxxxxxxxxxxxxx
Subject: Re: [geomesa-users] was location added as a new reserved word in geomesa 1.2.4 and beyond?

 

Hi Diane,

We added explicit checking for reserved words, as they can often cause problems later on due to geotools idiosyncrasies. The check is only performed when creating a new schema,
so if you are using an existing data set you should not be affected. You can override the check by setting user data in the simple feature type before calling createSchema:

sft.getUserData().put("override.reserved.words", "true")

Thanks,

Emilio

On 09/06/2016 03:20 PM, Diane Griffith wrote:

So we had been using location as a field in a schema for a data source.  This source has been ingested for quite some time.  Recently I upgraded to 1.2.4 on a dev instance but did not test ingest of this source I guess.  I just found that I cannot ingest with a schema that says location. 

 

So are you all adding reserved words as you release new versions?  Is there a work around regarding these reserved words…anyway I can use the word location still in my schema?  Last I remember I cannot remove fields from a schema, just add new fields on the end.  So do I have no other options except to redo this catalog and rework our schema/data stream for this data source?

 

Thanks,

Diane




_______________________________________________
geomesa-users mailing list
geomesa-users@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.locationtech.org/mailman/listinfo/geomesa-users

 

Back to the top