xtdb 2024-04-25 | Slack Archive

Cameron16:04:55

Hi @taylor.jeremydavid, Is there a precedent for using 1.x with metabase? I noticed there is an older looking driver implementation. I'm also wondering if there is an angle with the SQL extension? Otherwise, I have just planned to project some data out to a small postgres db for analytics for this particular project.

refset16:04:29

Hey @U2M723H42 I've had the integration mostly working previously using the (Calcite) SQL module in 1.x, to the point where it seemed to work okay for demos at least (~2y ago), but nobody on this team has pushed the approach very far since then to the point that we could confidently say it's 'supported' - sorry! Happy to help guide you if you are curious to test out the approach though. Exporting to a small Postgres DB would probably be faster & less risky unless you have a huge amount of very complex data and would rather avoid the schema mapping pain

Cameron16:04:54

Yep I figured, just wanted a sanity check, thanks! I haven't looked into 2.x yet, is the story there improved?

👌 1

refset19:04:18

as it happens, we're currently in the process of enabling first-class support for metabase (via beefing up our Postgres wire protocol implementation) :)

Cameron19:04:31

ooooh very nice

☺️ 1

nivekuil23:04:17

inserting complex lists (clojure code) gives an unexpected error:

{:xt/id 1 :data '(())}

1. Unhandled java.lang.IllegalArgumentException
   Lists have one child Field. Found: none

        Preconditions.java:  205  org.apache.arrow.util.Preconditions/checkArgument
           ListVector.java:  116  org.apache.arrow.vector.complex.ListVector/initializeChildrenFromFields
                Field.java:  111  org.apache.arrow.vector.types.pojo.Field/createVector

refset17:04:13

hey @U797MAJ8M thanks for reporting - I've opened an issue: https://github.com/xtdb/xtdb/issues/3341

FiVo13:06:52

Hey, should be fixed in the next release.

2024-04-25

Channels