Meltano v1.28.0 is Now Available

Meltano version 1.28.0 is now available, with a bug fix and an improvement to the command line interface.

Curious what else we got done last week? Check out the release post for last Thursday’s v1.27.1 (and v1.27.2, and v1.27.3), and our weekly sprint review.

New

  • #1937 Add optional plugin_type argument to meltano install to only (re)install plugins of a certain type

Fixes

  • #1938 Display error message when viewing dashboard before pipeline has run

Meltano v1.27.3 is Now Available

Meltano version 1.27.3 is now available, with various UX improvements, bug fixes, and changes behind the scenes.

Meltano version 1.27.1 was also released earlier today, but contained two regressions that were addressed in versions 1.27.2 and 1.27.3.

New

  • #1477 Allow read-only mode and authentication to be used at the same time, to allow anonymous read-only access and only require authentication for write actions.
  • #1914 Allow default dashboards and reports to be updated in place if package contains snapshots of older versions
  • #1933 Allow Meltano UI Google Analytics ID to be overridden using environment variable

Changes

  • #1896 Set pipeline update interval to daily by default, to start after first successful manual run
  • #1888 Explain in “Edit Connection” button tooltip why it may be disabled
  • #1890 Clarify that changing Start Date requires a new pipeline to be set up
  • #1892 Clarify in Run Log modal that the “Explore” button can also be found on the Connections page
  • #1891 Show data source logo and label in Run Log modal header instead of pipeline ID
  • #1893 Hide “Download Log” button while pipeline is running instead of disabling it
  • #1894 Suggest connecting a data source on Pipelines page when there are no pipelines yet
  • #1912 Suggest user gets in touch if the report they’re looking for is not included by default

Fixes

  • #1911 Display “Last updated: Updating…” instead of “Last updated: 1969-12-31” on reports while pipeline is running
  • #1910 Fix pipeline “Start date” and report “Data starting from” off-by-1 errors caused by timezone differences

Meltano v1.27.0 is Now Available

Meltano version 1.27.0 is now available, with various bug fixes and set up flow improvements.

Changes

  • #1909 Suggest disabling ad blocker if request related to an Ads or Analytics extractor was blocked by browser
  • #1886 Don’t prepopulate date fields that are not required and are better left blank
  • #1887 Hide End Date fields in connection setup since our end-users will want to import everything
  • #1905 Hide Google Analytics Reports field from UI since startup founder end-users will stick with default

Fixes

  • #1920 Fix extractor logo on Google Analytics Explore page
  • #1895 Fix bug causing newly created pipeline not to show as running when it is
  • #1906 Fix “Test Connection” for extractors that require a file to be uploaded, like Google Analytics
  • #1931 Validate uploaded file path when saving or testing connection settings

Meltano v1.26.1 and v1.26.2 are Now Available

Meltano version 1.26.1 is now available, with a more focused and less broad set of supported data sources on hosted instances, and improved support for date range filters on embedded reports and dashboards.

Meltano version 1.26.2 fixes a regression introduced in v1.26.1.

Changes

  • #1854 Remove non-marketing-sales data sources from UI
  • #1881 Store in system database when user was last active
  • #1846 Freeze reports with relative date filters in time when shared or embedded
  • #1847 Show date range on embedded reports and dashboards
  • #1847 Show date range on reports on dashboards

Meet the team: Douwe

As you’re getting to know Meltano, and as we are getting to know you and your company’s needs, we thought it would be appropriate for you to also get to know our team a little bit better!

And for the moment, that team is me: Douwe Maan.

I was born and raised in the Netherlands, currently live in Mexico City, and started working at GitLab a little over 5 years ago. Meltano, as you might know, is a project of GitLab, being operated as an internal startup.

I joined GitLab as a developer straight out of college when the company was just 10 people in size (we’re 1200+ now, in 67 different countries!). A few months later, I was tasked with hiring more developers, and once the team had doubled in size of couple of times and we started to run into the limitations of the flat organizational structure at scale, I became the first Development Lead.

Over the following years, the product and engineering organizations continued to grow, and existing teams were split up and new teams were created. The name of my team and the scope of its responsibility changed roughly every 9 months, until we were left with what I like to think of as GitLab’s core functionality: Source Code Management, pretty much everything related to managing and exploring Git repositories and collaborating using merge requests.

Since this had always been the part of GitLab dearest to my heart, it was great to now have a full team dedicated to it: more people working on improving the features in this area than had been at the entire company when I originally came on board.

By this point, though, the tiny startup I had joined 4 years before had grown 100x and was now a serious tech company; still an amazing and positively unique place to work, but quite a different beast than what I had initially been attracted to. With my team now finally dedicated to nothing but my favorite part of GitLab, I felt like my time in GitLab’s engineering organization had reached its natural final chapter, and I started thinking about what I would like the next chapter to say.

And that’s where Meltano came in: an internal startup at GitLab, working remotely and according to the GitLab values, but with a totally different product area and tech stack, and a team of just 5 people, that was looking for someone to lead and strengthen its engineering team. In other words, a match made in heaven for me: an opportunity to take everything that I had learned about engineering at startups, 1000-people tech companies and everything in between, and to use it to help grow what had (and has!) the potential to be GitLab’s second major product.

And so, in September 2019, I left GitLab’s engineering organization (but not the company) and joined General Manager Danielle, Backend Engineers Yannis and Micael, and Frontend Engineers Derek and Ben at Meltano.

After 6 months on the team, it was decided earlier this month that Danielle and the others would start looking for other opportunities inside GitLab (and out) where their skills and experience are in higher need right now, with me remaining on and leading the Meltano project solo for the time being.

I have tremendously enjoyed working with and learning from all of them, and I am honored and humbled to be given the opportunity to carry this project and their contributions forward on a path that was started by them and others long before I came on board and that we have continued to refine together over time.

While we haven’t quite been able to find product-market fit yet, we have experienced significant interest from startup founders all around the world and are working closely with them every day to find out where and how we can deliver the most value to help them run and find success with their businesses.

If you would like to see your startup sales funnel, analyzed, and are interested in a single set of dashboards and reports for the entire journey from ad impression to website visitor to successful sale to help you figure out what works, what doesn’t, what to scale up, and what to ramp down, please give Meltano a try, and don’t hesitate to get in touch if there is anything I can do to improve your experience!

Meltano v1.26.0 is Now Available

Meltano version 1.26.0 is now available, with various improvements and bug fixes.

If your Meltano instance is hosted on MeltanoData.com, it will have been upgraded automatically. For instructions on upgrading a self-hosted installation, check out the documentation.

Changes

  • #1188 Allow sorting by timeframe period columns (e.g. “Creation Date: Month”, “Creation Date: Year”)
  • #1873 Display error message when viewing model/design/report before pipeline has run
  • #1874 Print full error when initial model compilation fails
  • #1875 Automatically run query when sorting is changed
  • #1876 Don’t store Analyze UI state in report file
  • #1877 Allow designs to reference the same table more than once
  • #1878 Recompile models when meltano is upgraded