Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

ChDB: Embedded OLAP SQL Engine Powered by ClickHouse

github.com

Post reply on HN
Print view View original

21–30 of 35 posts

Re: ChDB: Embedded OLAP SQL Engine Powered by ClickHouse

#21

Post by maxmcd »

simonw wrote: post #18
pachico wrote: post #12

Earlier quoted context omitted.

I'm tempted to say that the very same reason why you need different environments is precisely because the package system is not healthy. And the fact that it's not easy to use doesn't really make things better.

What packaging systems are there that don't encourage different environments for different projects? I think Python's biggest weakness on this front is mainly that virtual environments came along too late - if they'd been designed into how pip etc worked from the beginning we would be in much better shape.

Any os-level package manager. Also: "npm -g", "pip install", "cargo install", etc..

Lots of programming languages or build systems will look for dependencies in globally-known locations.

Other than cargo, python's virtualenv, node_modules, and some other modern languages/systems I would imagine most are not project-scoped. Go had a single global dependency tree until go.mod, etc...

Re: ChDB: Embedded OLAP SQL Engine Powered by ClickHouse

#22

Post by texodus »

tempest_ wrote: post #20
bluehat974 wrote: post #9

Do they provide wasm version to use in browser? (like duckdb-wasm)

What is the use case for a browser based OLAP database ?

Something like https://github.com/finos/perspective ? We use an OLAP(-y) WASM engine to provide query-ability to our data visualization tool, and doing the calculations in the browser is cheaper and simpler than a server-side database for datasets that fit in browser memory.

Re: ChDB: Embedded OLAP SQL Engine Powered by ClickHouse

#23

Post by SahAssar »

maxmcd wrote: post #21
simonw wrote: post #18

Earlier quoted context omitted.

What packaging systems are there that don't encourage different environments for different projects? I think Python's biggest weakness on this front is mainly that virtual environments came along too late - if they'd been designed into how pip etc worked from the beginning we would be in much better shape.

Any os-level package manager. Also: "npm -g", "pip install", "cargo install", etc.. Lots of programming languages or build systems will look for dependencies in globally-known locations. Other than cargo, python's virtualenv, node_modules, and some other modern languages/systems I would imagine most are not project-scoped. Go had a single global dependency tree until go.mod, etc...

"npm" is a environment/scoped package manager. Saying "npm -g" when -g is a flag tell it to run in a non-default way (globally) is a bad argument.

Re: ChDB: Embedded OLAP SQL Engine Powered by ClickHouse

#24

Post by ryadh »

wodenokoto wrote: post #19

Is there a command line tool as well, or do I need to access it via Python?

ChDB is the in-process version for Python. You can try clickhouse-local if you want a CLI experience, or clickhouse-client against a clickhouse-server for the server experience

https://clickhouse.com/docs/en/operations/utilities/clickhou... https://clickhouse.com/docs/en/getting-started/quick-start

Re: ChDB: Embedded OLAP SQL Engine Powered by ClickHouse

#26

Post by justinsaccount »

simonw wrote: post #8

I absolutely love this trend of "pip install x" as a distribution mechanism for this kind of thing. People badmouth Python packaging a lot, but once you've learned how to use a virtual environment (admittedly a steeper learning curve than I'd like it to be) having binary wheels for so much of this kind of stuff is a huge win. See also Playwright, DuckDB, ziglang... I wrote a bit about those here https://simonwillison…

It's not really a good trend when you want to know exactly what is being installed.

https://hpc.guix.info/blog/2021/09/whats-in-a-package/

Re: ChDB: Embedded OLAP SQL Engine Powered by ClickHouse

#27

Post by adulion »

qxip wrote: post #14
adulion wrote: post #2

why would you use this over duckdb?

Disclaimer: I am a chdb maintainer! duckdb is currently thinner and has lots of active contributors and mature integrations, while chdb is still in its early stages BUT if you already love ClickHouse (like we do) chdb is a great choice as it inherits all the ClickHouse stability, performance and more importantly, all the 70+ supported formats for the embedded use case without any of the server/client requirements, ma…

does chdb have support for recursive CTES?

It and the ability to do `from 'https://example.com/.csv` is why i love duckdb

Re: ChDB: Embedded OLAP SQL Engine Powered by ClickHouse

#28

Post by richraposa »

adulion wrote: post #27
qxip wrote: post #14

Earlier quoted context omitted.

Disclaimer: I am a chdb maintainer! duckdb is currently thinner and has lots of active contributors and mature integrations, while chdb is still in its early stages BUT if you already love ClickHouse (like we do) chdb is a great choice as it inherits all the ClickHouse stability, performance and more importantly, all the 70+ supported formats for the embedded use case without any of the server/client requirements, ma…

does chdb have support for recursive CTES? It and the ability to do `from ' https://example.com/.csv ` is why i love duckdb

ClickHouse 10 years before DuckDB existed:

SELECT * FROM url('https://example.com/*.csv')

Re: ChDB: Embedded OLAP SQL Engine Powered by ClickHouse

#29

Post by adulion »

richraposa wrote: post #28
adulion wrote: post #27

Earlier quoted context omitted.

does chdb have support for recursive CTES? It and the ability to do `from ' https://example.com/.csv ` is why i love duckdb

ClickHouse 10 years before DuckDB existed: SELECT * FROM url(' https://example.com/*.csv ')

not as simple as from 'a.csv' and 10 years without recursive CTES?

Re: ChDB: Embedded OLAP SQL Engine Powered by ClickHouse

#30

Post by apavlo »

qxip wrote: post #14
adulion wrote: post #2

why would you use this over duckdb?

Disclaimer: I am a chdb maintainer! duckdb is currently thinner and has lots of active contributors and mature integrations, while chdb is still in its early stages BUT if you already love ClickHouse (like we do) chdb is a great choice as it inherits all the ClickHouse stability, performance and more importantly, all the 70+ supported formats for the embedded use case without any of the server/client requirements, ma…

Where can I find an SVG version of this logo? https://github.com/chdb-io/chdb/raw/main/docs/_static/snake-...
Post reply on HN