Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
salsakran
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
11 ms
·
61.
▲
by
salsakran
11y ago
Many of the listed sites almost certainly block Tor to prevent large scale scraping.
62.
▲
by
salsakran
11y ago
Looks very interesting! Would you be interested in helping us write a SnappyData connector for Metabase? github.com/metabase/metabase
63.
▲
Analytics rumblings in the public markets in 2015
(metabase.com)
1 points
by
salsakran
11y ago
|
0 comments
64.
▲
How to ruin your life with data
(metabase.com)
5 points
by
salsakran
11y ago
|
0 comments
65.
▲
The Push and Pull of Analytics
(metabase.com)
3 points
by
salsakran
11y ago
|
0 comments
66.
▲
by
salsakran
11y ago
precisely. (author of the post)
67.
▲
by
salsakran
11y ago
The fact that it wasn't an ORM was a huge win. We effectively had to build a dynamic ORM that modeled our end user's data warehouses which is a very different problem than a normal web app's database access patterns.
68.
▲
by
salsakran
11y ago
It's not hat "homebrew install gcc? pip install foo" is hard for us, it's that we didn't want to support 1000s of people trying to set it up on their machines. Every possible source of error we eliminated meant we&#
69.
▲
by
salsakran
11y ago
Off the cuff, I'd estimate that between the team members at the time, we'd shipped perhaps 100k+ LOC of java into production systems at past jobs. It didn't seem interesting to rehash why we didn't want Java's verbo
70.
▲
by
salsakran
11y ago
It sounds innocuous, but we were planning on supporting a lot more databases, and when you start needing to build drivers for MySQL, Postgres, SQL Server, Oracle, Redshift, etc etc anything that makes this step more brittle starts to add up
71.
▲
by
salsakran
11y ago
Hey - Really appreciate you taking the time to try it out! If you're still around, are you using the default schema ('public') for your tables? We've found a few bugs around non-default schema we're working on.
72.
▲
by
salsakran
11y ago
If you don't mind, cast a vote in https://github.com/metabase/metabase/issues/1294 We're going to be building out connectors by community demand. =)
73.
▲
by
salsakran
11y ago
Could you take a screenshot of what it looks like and leave a post on with it on http://discourse.metabase.com/ I'll try to reproduce it. What database are you using?
74.
▲
by
salsakran
11y ago
Really strange. Out of curiosity what version of OS X are you on? If you don't mind filing an issue at https://github.com/metabase/metabase/issues/new or http://discourse.metabase.com/ w
75.
▲
by
salsakran
11y ago
it looks like the field isn't marked as an FK in our semantic model. Could you go the admin, and click on "Metadata" and check to see what "special type" that field is marked at? If it's not "Foreign Key&q
76.
▲
by
salsakran
11y ago
Dumb question, but what dialect of SQL does the JDBC interface use?
77.
▲
by
salsakran
11y ago
Splunk is mainly about log analysis, though they have a new BI product. It's primarily about making sense of your logs. We primarily work with a database you already have (and eventually the data warehouse you'll spin up). Palanti
78.
▲
by
salsakran
11y ago
Thanks! We ship a sample database to play with in all the distributions.
79.
▲
by
salsakran
11y ago
Oh, that's an old version tag. Keep an eye out for a new version in a few hours, the app should offer you a chance to update. Regarding FK's we let you filter or group by any attribute on either the table you're working with
80.
▲
by
salsakran
11y ago
Let us know what you think!
81.
▲
by
salsakran
11y ago
Yes, writing the app in Clojure has been very interesting. Some things were downright magical, while other aspects felt very rough coming from other languages and frameworks. Ironically the prototype was in django =) There will be a blog po
82.
▲
by
salsakran
11y ago
Are you on virtualbox? Sounds like a port binding issue. If you open an issue at github.com/metabase/metabase or http://discourse.metabase.com/ we'll try to debug exactly what's happening.
83.
▲
by
salsakran
11y ago
So in practical terms, you'll eventually want to bring everything back in and create a analytics DB or data warehouse. Depending on what your schemas look like in each microservice, you might just be able to add each DB into Metabase a
84.
▲
by
salsakran
11y ago
easter eggs to come =)
85.
▲
by
salsakran
11y ago
We occasionally see failures to deploy when things don't spin up fast enough. Does it blow up every time you click on the deploy button?
86.
▲
by
salsakran
11y ago
Thanks for the kind words!
87.
▲
by
salsakran
11y ago
Redshift, Druid and Presto are in planning, but in general, we're going to build drivers in the order of community demand. If you have a specific db, open an issue or chime in on one of the open driver issues letting us know it's
88.
▲
by
salsakran
11y ago
Yes, we're mainly focused on making it easy for non-technical people to pull data out. We have had embedded applications that hit a REST api to expose actions on the data that was embedded though.
89.
▲
by
salsakran
11y ago
We run it on linux in production and it's the primary platform we recommend for company wide deployments. Power BI is pretty awesome, but pretty complicated when we tried it out. With enough attention it can do very cool things. Our pr
90.
▲
by
salsakran
11y ago
Yup, TR has a bioinformatics DB they sell which I think is based on metabase.org. We're in a sufficiently different space that we're hoping it's not a conflict. We don't explicitly support snowflake schemas but folks are
More ›