DataRobot Unveils Major Milestones, Including $300M Series G Funding Investment, Acquires Algorithmia (July 2021).Dataiku Series E: Unleashing Everyday AI ($400 million, August 2021).Redata:We raised our pre-seed round (August 2021).Hightouch has raised a Series A ($12 M, July 2021).Monte Carlo Raises Series C, Brings Funding to $101M to Help Companies Trust Their Data ($60 M, August 2021).Insight Partners leads $30M round into Metabase, developing enterprise business intelligence tools (August 2021).Preset Raises $35.9M Series B to Democratize Business Intelligence (August 2021).Grafana Labs Raises $220M to Accelerate Global Adoption and Development of Open Source Visualization and Observability Platform (August 2021).Introducing Tabular: Aim is to build a new kind of data platform around Apache Iceberg.Ahana $20M Series A – Furthering our Vision of Open Data Lake Analytics with Presto (August 2021).Treeverse raises $23M to bring Git-like version control to data lakes (July 2021).Databricks Raises $1.6 Billion Series H Investment at $38 Billion Valuation (August 2021, Previous round: February 2021).It's also worth mentioning the launch of Voltron Data by Wes McKinney and Josh Patterson to further develop the Apache Arrow ecosystem and the $200M Couchbase IPO. It's interesting to see that the 2 major open source data visualization companies raised funds during the period: Preset (creators of Apache Superset, $39.5M) and Metabase ($30M). The list includes the 1.6 billion raise by Databricks and large rounds for Dataiku ($400M), Datarobot ($300M) and Grafana Labs ($220M).
The issue is that you are using a datetime column in MySQL which doesn't have an associated timezone.July and August were again quite active months, with 13 notable fundraising events. Hope to see it fixed I spent some time digging into this problem yesterday and I think I have a pretty good idea of what the problem is, but unfortunately I think it is not an easy fix.
But this one drawback is preventing full adoption by our team. Metabase is an amazing tool which has given us an unlimited number of dashboards and queries to use for free, as opposed to other commercial alternatives which have expensive quota limits. When I manually tweak the SQL to add the timezone offset - the useful features like X-Ray, group by week/month etc are not available anymore. If not, they have to depend on dev team to manually repair the SQL queries to get the correct data.Īnd also - it seems like X-Ray Features work on Timeline graphs only when they are generated via GUI. Isn't the Report timezone setting in Admin Panel supposed to add this offset to queries automatically? If that can be done, it will help us a lot - as we can let everyone in the company set up any question they want. `checked_out_on `, 'UTC ', 'Asia/Calcutta ')) = date(now())) `is_checked_out ` = TRUE) AND date(convert_tz( `cart `. `created_for_testing ` = FALSEĪND `cart `. SELECT count( *) AS `count ` FROM `cart ` WHERE (( `cart `. I have deliberately used the PREVIOUS date so the figures can be compared for the third part of my question This is the RIGHT query which should execute (which we are currently doing in SQL). This is shown by the fact that even after compensating for the diff in hours between the MB question and the SQL, the numbers do not match up. The data is not taking into account the 30 minute difference in times, it only considers whole hours.We do not get high numbers in the early morning hours. We know this because the pattern of the metrics is not correct. The hours being shown on the client are not on the client time, but the server time (UTC).This can be also be seen from the log which i have attached at the very end The data being selected is of the day PREVIOUS to the one being requested.The field in question, "Appointment Dt", is a DATETIME data type in mySQL I have created a question which groups a certain metric by the hour of day. #nohup java -Xmx1536m -Xms1536m -Duser.timezone=Asia/Calcutta -jar ~/current/metabase.jar & Running it on the server with the time zone set makes no difference Nohup java -Xmx1536m -Xms1536m -jar ~/current/metabase.jar & MB is running on the server without a time zone set Time zone on the client is set to Asia/Calcutta Metabase client is set to use India/Calcutta as the timezone. Metabase 26rc1, running on a EC2 with UTC.