Glad you've made some progress. Not sure why your <storage name>.public is how you have to go about things. Will have to give that some more thought. At least you're over that hurdle for the minute.
> 1. Uuid columns in postgres arent supported - I'll look to contribute code > to add support for this if its within my ability. > My gut is that you can do this only in Drill code. Is there an exception when you try to query or do they just not show up. If the former, than a Calcite change is also required. If you just get a warning in the log and the column is missing, then we only need to make changes in Drill's JdbcRecordReader to provide a JDBC Type => Drill Type mapping. Current mappings to be added to are here: https://github.com/apache/drill/blob/master/contrib/storage-jdbc/src/main/java/org/apache/drill/exec/store/jdbc/JdbcRecordReader.java#L90 > > 2. I've added views to convert the uuid columns to postgres 'text' data > types - but those aren't usable within JOINs in Drill. Is that something > you plan on fixing? I can cast to VARCHAR(?) but its a bit annoying and I > bet thats not very good for performance? > What kind of error do you get? Our current mapping is TEXT => VARCHAR so I'm not sure why the join is failing. Is this a join between two columns in Postgres or Posgres + Something else? (We push down joins that are all within Postgres.) > > 3. I'm having trouble following the instructions on > https://drill.apache.org/docs/using-the-jdbc-driver/ to get the JDBC > client up and running. I think the instructions might be out of date? It > references having your client use the driver from inside /jars > named drill-jdbc-all-<version>.jar but that no longer exists? Theres > just drill-jdbc-<version>.jar and drill-jdbc-storage-<version>.jar. Trying > either of those fails in my client (0xDBE) with: > The image was dropped (you can send to me directly if you like). The correct path is drill/jars/jdbc-driver/. It is possible you missed the "jdbc-driver" part. You'll need the drill-jdbc-all-* version as that includes all the dependencies required to make Drill work. We haven't tried using 0xDBE yet but things should work. Sorry Jacques, one last question for now - whats the best way for me to get > setup for (1)? Is calcite forked within the drill repo or do I need to pull > both projects locally and statically deploy jars from my fork of calcite to > test in drill? Or can I test calcite in isolation? > We're still forked. The current version is here: https://github.com/dremio/calcite/tree/DrillCalcite1.4.0 You'll need to do the local deploy for each to make them work together. There are tests in Calcite for its JdbcAdapter (which Drill leverages) so fixes for Schema related issues should be possible to test solely within Calcite. Let me know about what is happening with the UUID column so I can give you a better direction on steps to take. thanks, Jacques
