Fork me on GitHub
#onyx
<
2017-05-27
>
lucasbradstreet07:05:13

@stephenmhopper sorry about the delay, forgot about the build. You can try 0.10.0.0-20170526.222812-24

lmergen13:05:20

@lucasbradstreet @michaeldrogalis in addition to the small patch i just submitted that batches multiple inserts (which will give significant performance improvements to users), i’m planning to make some postgresql-specific improvements that will use a COPY statement rather than inserts using org.postgresql.jdbc.CopyManager i think it would be valuable to others that are doing ETL with onyx and just want to use an SQL database but are having problems making their writes scale. i think it could open up a whole range of possibilities. however, i’m not sure onyx-sql is the right place to do this. do you have any thoughts on this ?

lucasbradstreet19:05:19

@lmergen that’s awesome. I’ve wanted that for ages, but we haven’t really focused on SQL enough yet.

lucasbradstreet19:05:29

@lmergen I’d be happy to have it as part of onyx-sql

lmergen19:05:39

say no more!

lucasbradstreet20:05:01

@lmergen is onyx-sql working well now so far? I can merge your PR soon if so

lmergen20:05:23

writes are stable, am not using reads

lucasbradstreet20:05:25

ah yeah, I need to fix the tests. That’s why I haven’t merged it

lucasbradstreet20:05:40

tests are only broken because of schema issues

lmergen20:05:00

i think the uuid test is broken as well

lmergen20:05:15

which makes sense :)

lucasbradstreet20:05:16

Right, yeah, uuids selects are completely disabled currently

lmergen20:05:21

hmmm, are many people using it ?

lucasbradstreet20:05:24

some, but onyx-sql hasn’t worked on 0.10 for a while, so this is still progress.