pauldix

10 ms·

61.
The plan for InfluxDB 3.0 Open Source(influxdata.com)
12 points by pauldix 3y ago|6 comments
62.
by pauldix 3y ago
I went here in November 2001 right after it opened. It was my first time in NYC. I loved it, thought it was so cool. After that trip I decided I’d have to live in this city at some point. Moved here in 2005 and been in NYC ever since. Remot
63.
by pauldix 3y ago
It's a terrible situation and we failed on many levels on this one. We will improve our process from here and conduct a more full post mortem.
64.
by pauldix 3y ago
We get an email address because we need to contact our customers. After that we make best efforts but if people can’t respond to vendors they pay money to, we’re really at a loss. I realize that shutting down a region isn’t good. It’s not w
65.
by pauldix 3y ago
Hi, cofounder and CTO here. We notified everyone via email on February 23, April 6 and May 15th. We also offered to help migrate all users. I realize that it's not ideal that we've shut down this system, but we made our best effor
66.
by pauldix 3y ago
It's built around the arrow-rs library, which we've contributed to significantly: https://github.com/apache/arrow-rs
67.
by pauldix 3y ago
The open source build will be using the libraries of what we have in our production system, but it'll be a single server release, which isn't something we're running in production. So while many components are things we'
68.
by pauldix 3y ago
For new users we are suggesting they use either InfluxQL or SQL. Both are supported natively in 3.0 and we'll continue to support them. We were able to bring InfluxQL support because of its similarity to SQL. We were able to build an I
69.
by pauldix 3y ago
InfluxDB 3.0 is built around a columnar query engine (Apache DataFusion) with data stored in Parquet files in object storage. Eliminating cardinality concerns was one of the top drivers for creating 3.0. I mention some of the other big thin
70.
by pauldix 3y ago
We'll be releasing an alpha of InfluxDB 3.0 open source later this year. I'm actually personally on the hook for this one while our engineering team is focused on our cloud and on-premise commercial offerings. So it's planned
71.
by pauldix 3y ago
This is a difficult one to answer succinctly, but I'll leave some quick thoughts. One of the things that made this tricky is that we weren't just replacing some small system with a single API. We fundamentally changed the underlyi
72.
by pauldix 3y ago
The differences in 2.x and 3.x are quite significant. The 3.0 database was a ground up rewrite in a new language (v1 and v2 were in Go, v3 is in Rust). InfluxDB v2 was all about the Flux language and a much broader set of API capabilities a
73.
by pauldix 3y ago
Hello, one of the authors here, happy to answer any questions!
74.
by pauldix 3y ago
Likely the 3 founders have 12% each (after a 4 year vest) and the remainder (21%) goes to the option pool.
75.
by pauldix 3y ago
We're still figuring out what will be in InfluxDB 3.0 open source. For now we're focused on our cloud offering where we can iterate and debug more quickly. We expect that the open source will fill a different need than the cloud p
76.
by pauldix 3y ago
Yeah, if it's getting astroturfed and pushed up artificially that's definitely cause to flag it. It's just a shame that happened because this almost certainly would have landed on the front page on its own.
77.
by pauldix 3y ago
Shame that this is flagged, I think this is a really exciting development and was hoping to see the discussion around it. Open sourcing the fine tuning training set is a great building block. Will be exciting to see if others continue to bu
78.
Inventing Reality Documentary from Matt O'Dowd of Space Time(indiegogo.com)
2 points by pauldix 4y ago|0 comments
79.
by pauldix 4y ago
I would guess that it's mostly because of tooling and library availability. There has been very little cross language support for reading and writing Parquet files. Mostly it was concentrated in Java and C++. But since it fell under th
80.
Querying Parquet with Millisecond Latency(influxdata.com)
6 points by pauldix 4y ago|3 comments
81.
by pauldix 4y ago
DataFusion is great, we're happy to be contributing to it. Also excited to see so many people around the world picking it up and contributing as well. With our development efforts on IOx, it's like a strong tailwind. But we put a
82.
by pauldix 4y ago
Hi, post author and founder of InfluxDB here. We're supporting Flux (our scripting and query language), InfluxQL (our original SQL like language), and SQL (specifically the Postgres dialect as that's what DataFusion supports). The
83.
by pauldix 4y ago
Congrats Garry! So well deserved. I feel so lucky to have had your help as a group partner when we went through W13 as Errplane (hah, good thing we figured out something to pivot to). YC changed my life too and I can't imagine it in be
84.
by pauldix 5y ago
More good news for Apache Arrow and any projects building around the standard. Excited to see more tools, clients, servers, and everything in between support Arrow, Arrow Flight, Arrow Flight SQL, and Parquet! Over the next few years I hope
85.
Voltron Data grabs $110M to build startup based on Apache Arrow project(techcrunch.com)
29 points by pauldix 5y ago|2 comments
86.
by pauldix 5y ago
Oh, and for anyone interested in pitching in on the Rust implementation, there's an issue logged here along with some discussion: https://github.com/apache/arrow-rs/issues/1323
87.
by pauldix 5y ago
This is great and makes a ton of sense as a refinement to their work on Flight previously. InfluxDB IOx already supports Flight, but we'll almost certainly be updating to support Flight SQL before we launch. We've been thinking ab
88.
by pauldix 5y ago
Sales: Boiler Room, Glengary Glen Ross Inspiration: Free Solo (watching someone with singular focus that achieves excellence, it's absolutely incredible) Tech: meh, not sure much does it here. Tons of entertaining stuff, but not sure w
89.
by pauldix 5y ago
The new core we're building for InfluxDB (named InfluxDB IOx) uses Datafusion for query execution. We have multiple team members contributing to this release and we're super excited to be involved with it. I think it's a real
90.
by pauldix 5y ago
The Grafana Enterprise point is the most salient here. The answer is no, they wouldn't have been able to create closed source plugins for a commercial product. Only AGPL code. As I've stated before: copyleft licenses are an evolut

More ›