A complete solution for open data platforms, enterprise data catalogs, data lakes and data management. Open source, mature, fully-featured and production ready.

DataHub

I am executing ingest via docker container(linkedin/datahub-ingestion). But, am running into this issue here:
```'error': 'Unable to emit metadata to DataHub GMS',
               'info': {'exceptionClass': 'com.linkedin.restli.server.RestLiServiceException',
                        'message': "No root resource defined for path '/datasets'",
                        'stackTrace': 'com.linkedin.restli.server.RestLiServiceException [HTTP Status:404]: No root resource defined for path '
                                      "'/datasets'\n"```

<@U01Q3UZBD38>: you might be using the `:latest` tag on the image. We have moved away from using `:latest` tags on images to `:head` .

thanks <@UV0M2EB8Q> that was the trick, somehow I missed that. Ingestion now works, but I postgis raster columns are still not being correctly mapped:
```gama-datahub-t4n98: {'failures': {},                                                                                                                                                 
gama-datahub-t4n98:  'filtered': ['cron.*', 'information_schema.*', 'tiger.*', 'topology.*'],                                                                                        
gama-datahub-t4n98:  'tables_scanned': 164,                                                                                                                                          
gama-datahub-t4n98:  'views_scanned': 4,                                                                                                                                             
gama-datahub-t4n98:  'warnings': {'gama-pg-db.ethiopia.etnahil1': ['unable to map type Raster() to metadata schema'], ```

<@U02AYK6RSPP>: could you take a look when you have a chance?

Hi <@U01Q3UZBD38>, I will take a look and reply back.

<@U01Q3UZBD38> are you doing postgis ingestion using the postgres source? Currently not all of the sql sources we have support complex data types. postgis seems to be an extender for postgres so the new data types it comes with don't have support as of now.

OK, I see. Thanks <@UV0M2EB8Q> and <@U02AYK6RSPP>