Fork me on GitHub
#xtdb
<
2019-09-04
>
refset16:09:00

Hey folks, I hope you all enjoy using the new 19.09-1.4.0-alpha release featuring extensive JDBC support. It opens up a lot of configuration combinations that will take a while to document comprehensively but we'll get there. Thank you for your continued interest!

👍 8
4
dcj18:09:08

Cool! I'm interested in trying Crux with an existing Postgres DB....

refset18:09:24

@U07TTE6RH perfect scenario 🙂

dcj18:09:56

@U899JBRPF: As a Crux newbie, I'll likely need to wait until the JDBC support is documented....

jonpither18:09:12

Docs are there, let us know if you have any issues https://juxt.pro/crux/docs/configuration.html#_jdbc_nodes

refset19:09:48

Also I posted some instructions for Postgres here last week:

(ns crux-jdbc-example
  (:require [crux.api :as crux])
  (:import (crux.api Crux ICruxAPI)))

(def opts {:dbtype "postgresql"
           :port 5432
           :dbname "postgres"
           :user "postgres"
           :kv-backend "crux.kv.memdb.MemKv"
           :db-dir "kv-store"})

(def node (Crux/startJDBCNode opts))
>>> in conjunction with running the standard postgres docker image using docker run -p 5432:5432 postgres

👍 4
hoppy19:09:02

can confirm that things seem to work well using postgres with a rocks-kv (at least for my simple testing)

👍 4
hoppy19:09:32

I got a good nip on the postgres schema change though 😀

refset19:09:13

@U19EVCEBV oops, sorry, yeah that probably deserved to be noted in the changelog at the very least...

hoppy20:09:36

I was playing with about 100K random(ish) entities, performance seemed decent enough.

hoppy20:09:01

I also wiped the rocks store and let it rebuild, and that seemed to work correctly as well.

parrot 4