Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document GeoServer naming restrictions wrt ingesting data #690

Open
ScottEvil opened this issue Mar 29, 2016 · 2 comments
Open

Document GeoServer naming restrictions wrt ingesting data #690

ScottEvil opened this issue Mar 29, 2016 · 2 comments
Milestone

Comments

@ScottEvil
Copy link
Contributor

GeoServer imposes restrictions on naming conventions and this has impact on namespace names. We need to document this so that GeoWave users & developers can understand the impacts of this.

This issue stems from the thread in: Issue #83

@rfecher
Copy link
Contributor

rfecher commented Mar 31, 2016

This related to #664

@datasedai
Copy link
Contributor

I think that the original issue, #83, really related to the gwNamespace, not the GeoServer namespace. If i make a gwNamespace with an invalid value, then accumulo will not be able to create the table. I'm not sure how we missed this during the scrub, but I recommend we update the description of this task to reflect.

I also recommend that we explicitly include in documentation definitions of the different namespaces.
gwNamespace vs. Accumulo namespace
gwNamespace vs. feature namespace

@datasedai datasedai added this to the Current milestone May 8, 2016
@datasedai datasedai modified the milestones: Future, Current May 16, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants