Error message when trying to query mongodb databse using superset meta database connection about superset HOT 5 CLOSED

Hopefully @betodealmeida can help a bit.

from superset.

This a driver issue? Drill issue? My guess is you can validate that it is the case with this simple python script (thanks gpt!)

from sqlalchemy import create_engine

engine = create_engine('drill://{{THE_CONN_STR_YOU_PUT_IN_SUPERSET}}')

with engine.connect() as connection:
    result = connection.execute("SELECT * FROM cat.schema.table")  # Replace 'your_table' with your actual table name
    for row in result:
        print(row)

from superset.

I found a workaround actually.
I prepare my dataset on Drill directly by writing my query, store it in parquet using Drill filesystem, then query the DFS on Superset. The only difference is that I wont have my data live as I need to recreate the dataset on Drill each time (I will use a seperate python job for that)

from superset.

Just a thought, but I've seen hacks that try to do best of both worlds (perf and realtime) by creating view that that UNION ALL as in

CREATE VIEW beat_of_both_worlds AS
SELECT * FROM highperf_materalized_table WHERE dt < DATE('{hard_coded_last_etl_job}')
UNION ALL
SELECT * FROM realtime_virtual_external table WHERE dt >= DATE('{hard_coded_last_etl_job}')

You need to make sure predicate is properly applied by the optimizer / excution-engine and leveraging some indexed/partitioned field, but it's doable in some systems.

from superset.

Closing for now as I'm pretty sure it's a driver/database error message, but feel free to reopen if it's not the case. The py script I posted above should make that clear, and could be used to open a ticket in the proper place.

from superset.