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

Add objectid as eligible id column by our content guesser #14965

Merged
merged 2 commits into from
Jun 20, 2019

Conversation

ethervoid
Copy link
Contributor

@ethervoid ethervoid commented Jun 12, 2019

Related https://github.com/CartoDB/support/issues/2077

We have some whitelisted columns the prevails after ogr2ogr imports the file: ogc_fid, gid and cartodb_id but when we included GDB files in our catalog we didn't include its own column objectid.

Objectid is the id column for that type of files and is taken by ogr2ogr as the id column so in the fix I've made, we now include it as ID column and we use it as our cartodb_id when the content guesser is activated

@gonzaloriestra gonzaloriestra self-assigned this Jun 13, 2019
@gonzaloriestra
Copy link
Contributor

gonzaloriestra commented Jun 13, 2019

❌ Acceptance failed

I've tried to follow the STR from the original issue, but it's showing the same errors... I'm trying in staging with the user gonzalor-gdb. Any idea?

@ethervoid
Copy link
Contributor Author

@gonzaloriestra the failure you're getting is related to GDAL not to the objectid problem we I think this is safe to be deployed

@gonzaloriestra
Copy link
Contributor

Right, it doesn't show the same error. Let's go then!

FileGDB files has objectid column as id column so we need to include
in our list of eligibles id to be able to import GDB using content
guesser
@ethervoid ethervoid merged commit 510b193 into master Jun 20, 2019
@ethervoid ethervoid deleted the s2077_gdb_id_imports branch June 20, 2019 14:45
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

Successfully merging this pull request may close these issues.

3 participants