Self Hosted. Can't import Airtable base

twicros · December 25, 2022, 4:00pm

I cant import base from AirTable
in 42% importing this error:

Same base success imported in baserow.io host version.

There is docker-compose logs:
celery-export-worker_1 celery-export-worker_1 celery-export-worker_1 celery-export-worker_1 celery-export-worker_1 celery-export-worker_1 celery-export-worker_1 celery-export-worker_1 celery-export-worker_1 celery-export-worker_1 celery-export-worker_1 celery-export-worker_1 celery-export-worker_1 celery-export-worker_1 celery-export-worker_1 celery-export-worker_1 celery-export-worker_1 celery-export-worker_1 celery-export-worker_1 celery-export-worker_1 celery-export-worker_1 celery-export-worker_1 celery-export-worker_1 celery-export-worker_1 celery-export-worker_1 celery-export-worker_1 celery-export-worker_1 celery-export-worker_1 celery-export-worker_1 | [2022-12-25 15:51:32,449: ERROR/ForkPoolWorker-1] Task baserow.core.jobs.tasks.run_async_job[f9225aa8-b89a-42a7-b3e9-493197e26c43] raised unexpected: KeyError(43)
| Traceback (most recent call last):
| File “/baserow/venv/lib/python3.9/site-packages/celery/app/trace.py”, line 451, in trace_task
| R = retval = fun(*args, **kwargs)
| File “/baserow/venv/lib/python3.9/site-packages/celery/app/trace.py”, line 734, in protected_call
| return self.run(*args, **kwargs)
| File “/baserow/backend/src/baserow/core/jobs/tasks.py”, line 73, in run_async_job
| raise e
| File “/baserow/backend/src/baserow/core/jobs/tasks.py”, line 36, in run_async_job
| JobHandler().run(job)
| File “/baserow/backend/src/baserow/core/jobs/handler.py”, line 62, in run
| return job_type.run(job, progress)
| File “/baserow/backend/src/baserow/contrib/database/airtable/job_type.py”, line 118, in run
| databases, id_mapping = AirtableHandler.import_from_airtable_to_group(
| File “/baserow/backend/src/baserow/contrib/database/airtable/handler.py”, line 609, in import_from_airtable_to_group
| databases, id_mapping = CoreHandler().import_applications_to_group(
| File “/baserow/backend/src/baserow/core/handler.py”, line 1344, in import_applications_to_group
| imported_application = application_type.import_serialized(
| File “/baserow/backend/src/baserow/contrib/database/application_types.py”, line 445, in import_serialized
| self.import_tables_serialized(
| File “/baserow/backend/src/baserow/contrib/database/application_types.py”, line 289, in import_tables_serialized
| view_type.import_serialized(
| File “/baserow/backend/src/baserow/contrib/database/views/view_types.py”, line 131, in import_serialized
| grid_view = super().import_serialized(
| File “/baserow/backend/src/baserow/contrib/database/views/registries.py”, line 346, in import_serialized
| value_provider_type.set_import_serialized_value(
| File “/baserow/premium/backend/src/baserow_premium/views/decorator_value_provider_types.py”, line 127, in set_import_serialized_value
| new_field_id = id_mapping[“database_fields”][filter[“field”]]
| KeyError: 43

joffcom · December 25, 2022, 8:42pm

How many records and columns do you have? It looks like it is an issue with a column so maybe a type has been set that isn’t right or something.

twicros · December 26, 2022, 2:22am

I have many row and colomns. But same base was normaly import in baserow.io standart host

joffcom · December 27, 2022, 10:45am

That is odd, it may still be useful to know though as the error does seem to point towards a key.

Does it fail with other Airtable bases?

bram · December 27, 2022, 2:17pm

Hi @twicros, which version of Baserow are you self-hosting? The error seems like field id mapping error. I know we had some problems with that in the past, but it has all been fixed since. Could it be that you’re running an older version of Baserow? If so, then upgrading to the latest version will probably fix it.

twicros · December 28, 2022, 11:01am

My version is actual. I find reason.

I just run much faster server. 4 core CPU and 8 GB RAM. And it start working normaly. Thank you for your help!

joffcom · December 28, 2022, 11:15am

That is interesting to hear, thanks for coming back with a solution. Would still be interested in knowing how many rows and columns just to get a rough benchmark feel on it.

bram · December 28, 2022, 1:50pm

Glad to hear that it now works @twicros!

twicros · January 1, 2023, 4:17am

50 000 rows
~ 150 columns