id stringlengths 18 78 | source stringclasses 5
values | source_url stringlengths 41 100 | pipeline_layer stringclasses 2
values | title stringlengths 1 349 | body stringlengths 0 5k | solution stringlengths 0 3k | tools_mentioned listlengths 1 8 | cross_tool bool 2
classes | labels listlengths 0 5 | category stringclasses 34
values | score int64 0 94 | comments_count int64 0 41 | state stringclasses 5
values | timestamp stringlengths 0 20 | repo stringclasses 13
values |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
gh-meltano-meltano-9900 | github_issues | https://github.com/meltano/meltano/issues/9900 | ingestion | bug: Cannot set `executable` per-environment | ### Meltano Version
4.1.2
### Python Version
3.11
### Bug scope
Configuration (settings parsing, validation, etc.)
### Operating System
_No response_
### Description
Hi! We recently migrated from ver 2.19 to 4.1.2 and noticed that our dbt-snowflake `utility` wasn't using the `executable` configured in the per-... | Hi @ralichkov!
Along the way we removed the ability to override non-settings per environment, since they unnecessarily complicated plugin auto-installation, virtualenv reuse, etc.
The recommended way to override a plugin's `executable` or `pip_url` is to use [inheritance](https://docs.meltano.com/concepts/plugins/#pl... | [
"meltano",
"dbt",
"snowflake"
] | true | [
"question",
"valuestream/Meltano"
] | meltano_errors | 0 | 3 | closed | 2026-03-12T16:50:24Z | meltano/meltano |
gh-meltano-meltano-9859 | github_issues | https://github.com/meltano/meltano/issues/9859 | ingestion | docs: Youtube video no longer available | ### Meltano Version
_No response_
### Python Version
None
### Bug scope
Documentation
### Operating System
_No response_
### Description
The video ["0 to DataOps" speedrun](https://www.youtube.com/watch?v=sL3RvXZOTvE), referenced in https://docs.meltano.com/guide/complete_tutorial/ seems to be unavailable.
ht... | Hi @jorgeegomez,
The video is no longer available, but we plan to publish a new version of it with the current workflow and outputs, which should be even simpler.
Sorry about the confusion! | [
"meltano"
] | false | [
"Documentation",
"question",
"kind/Bug",
"valuestream/Meltano"
] | meltano_errors | 0 | 3 | closed | 2026-02-19T04:14:18Z | meltano/meltano |
gh-meltano-meltano-9873 | github_issues | https://github.com/meltano/meltano/issues/9873 | ingestion | feature: Show a sensible subset of settings by default in meltano config list | ### Feature scope
CLI (options, error messages, logging, etc.)
### Description
`meltano config list` shows every setting for a plugin regardless of whether the user has configured it. For plugins with many settings, this buries useful information in noise. Most users checking their config only care about what they'v... | [
"meltano",
"postgres"
] | true | [
"cli",
"ux",
"kind/Feature",
"Settings"
] | meltano_errors | 1 | 0 | open | 2026-02-25T04:25:21Z | meltano/meltano | |
gh-meltano-meltano-9872 | github_issues | https://github.com/meltano/meltano/issues/9872 | ingestion | feature: Sort settings meaningfully in meltano config list | ### Feature scope
CLI (options, error messages, logging, etc.)
### Description
`meltano config list` displays settings in the order determined by plugin definition and inheritance, with no logical grouping by importance. For plugins with many settings, this produces a flat wall of text where user-configured settings... | [
"meltano",
"postgres"
] | true | [
"cli",
"ux",
"kind/Feature",
"Settings"
] | meltano_errors | 1 | 0 | open | 2026-02-25T04:25:17Z | meltano/meltano | |
gh-meltano-meltano-9851 | github_issues | https://github.com/meltano/meltano/issues/9851 | ingestion | feature: `.python-version` support | ### Feature scope
CLI (options, error messages, logging, etc.)
### Description
This would inform Meltano of which version to use by default for installing plugins in a project.
```
project
├── .python-version
└── meltano.yml
```
### TBD
- **Precedence**. The presence of `.python-version` (with a valid Python vers... | [
"meltano"
] | false | [
"needs refinement",
"plugin management",
"kind/Feature",
"valuestream/Meltano"
] | meltano_errors | 0 | 0 | open | 2026-02-16T05:30:52Z | meltano/meltano | |
gh-disc-meltano-meltano-9846 | github_discussions | https://github.com/meltano/meltano/discussions/9846 | ingestion | Deterministic Offline Security Auditing for Transparent DataOps | ### Problem:
  DataOps pipelines often manage a vast array of connectors, credentials, and infrastructure configurations.
  A single leaked secret or a misconfigured CI/CD workflow can lead to a massive data breach. Existing security
  tools often introduce "black-box" logic or requi... | Can you share any links to "Auditor Core" documentation? | [
"json",
"meltano"
] | true | [] | meltano_errors | 0 | 1 | open | 2026-02-11T11:31:19Z | meltano/meltano |
gh-disc-meltano-meltano-9845 | github_discussions | https://github.com/meltano/meltano/discussions/9845 | ingestion | Deterministic Security Gates for Data Pipelines (CI/CD Hardening) | As a DataOps orchestration platform, Meltano manages a vast landscape of connector configurations, API credentials, and infrastructure code. In such a high-stakes environment, a single compromised GitHub Action or an unpinned dependency can lead to a devastating supply-chain attack.
I have developed **Sentinel Core*... | Can you share any links to "Sentinel Core" documentation? | [
"meltano"
] | false | [] | meltano_errors | 0 | 1 | open | 2026-02-11T09:37:49Z | meltano/meltano |
gh-disc-meltano-meltano-9716 | github_discussions | https://github.com/meltano/meltano/discussions/9716 | ingestion | Select stream properties before the tap sends the request? | Hi, I'm a very novice programmer, it's safe to say I don't know anything about data science, so I apologize in advance for wasting your time.
I'm a trainee for 3 months in a healthcare environment and I have to build a pipeline to retrieve the data from a third party source for which we also have to build and sell the... | Welp... I just discovered that's what streams.params do, thank you for this awesome program.
```yaml
environments:
- name: dev
config:
plugins:
extractors:
- name: tap-rest-api-msdk
capabilities:
- discover
config:
api_url: h... | [
"json",
"meltano"
] | true | [] | meltano_errors | 0 | 1 | answered | 2026-01-05T14:41:39Z | meltano/meltano |
gh-disc-meltano-meltano-9778 | github_discussions | https://github.com/meltano/meltano/discussions/9778 | ingestion | Bug: meltano add fails during Git submodule update (gettext 0.22.5 usage error) | ### Meltano Version
4.0.8
### Python Version
3.12
### Bug scope
CLI (options, error messages, logging, etc.)
### Operating System
Linux - Ubuntu 22.04.5 LTS
### Description
Summary
Adding a plugin (e.g., tap-csv) fails during the installation phase. The root cause is a failure in the Git submodule update proce... | @avinashkurup can you share your (redacted) `meltano.yml` here to help me trying to reproduce the issue? | [
"csv",
"meltano"
] | true | [
"question",
"installation",
"plugin management",
"valuestream/Meltano"
] | meltano_errors | 0 | 5 | open | 2025-12-23T12:04:19Z | meltano/meltano |
gh-disc-meltano-meltano-9656 | github_discussions | https://github.com/meltano/meltano/discussions/9656 | ingestion | How to extract useful error messages from meltano cli output automatically | Hello, In the project i'm currently working on I am required to extract the reason for pipeline errors from the generated logfile. As of now I notice that log level errors don't actually have the reason why the pipeline fails. It only contains the stacktrace which doesn't point anywhere, while the more useful error mes... | Hi @JohnLkt 👋
> is there a way to force meltano to generate the actual error logs as level error?
Yes, it's supported for plugins based on the [Meltano SDK](https://sdk.meltano.com/) v0.50+: https://docs.meltano.com/guide/logging/#structured-log-parsing. | [
"meltano"
] | false | [
"Logging"
] | meltano_errors | 0 | 1 | open | 2025-11-27T03:50:24Z | meltano/meltano |
gh-disc-meltano-meltano-9369 | github_discussions | https://github.com/meltano/meltano/discussions/9369 | ingestion | Replace `requirements.txt` in new projects with (optional) `pyproject.toml` | ## TL;DR
Replace `requirements.txt` in new projects with (optional) `pyproject.toml`. The project file should be added by default but leave the door open for the user to skip it if, for example, they're managing their Meltano installation globally or through some other package manager (like [Mise](https://mise.jdx.d... | [
"meltano"
] | false | [
"cli",
"OKR: New User Experience"
] | meltano_errors | 0 | 0 | open | 2025-07-11T22:05:18Z | meltano/meltano | |
gh-disc-meltano-meltano-9349 | github_discussions | https://github.com/meltano/meltano/discussions/9349 | ingestion | Automatic metadata introspection for SDK-based taps and targets | ## Summary
It's currently not easy for tap developers to keep in sync their tap's configuration JSON schema and the Meltano metadata (`settings`, `capabilities`, etc.). This feature would make it easy to keep the custom plugin definition in `meltano.yml` in sync with the tap.
## CLI
```
meltano add tap-exampl... | [
"json",
"meltano"
] | true | [
"kind/Feature"
] | meltano_errors | 0 | 0 | open | 2025-07-03T18:24:19Z | meltano/meltano | |
gh-disc-meltano-meltano-9287 | github_discussions | https://github.com/meltano/meltano/discussions/9287 | ingestion | Meltano Office Hours - June 4th, 2025 | ### Time
4pm GMT / 11am EDT / 9am PDT
### Agenda
| Topic | Link |
|:--------|:-------|
| Behavior of `default_target_schema` for stream names of the form `foo-bar` | https://github.com/meltano/sdk/pull/3020 |
| [
"meltano"
] | false | [] | meltano_errors | 0 | 0 | open | 2025-05-28T00:17:05Z | meltano/meltano | |
gh-disc-meltano-meltano-9221 | github_discussions | https://github.com/meltano/meltano/discussions/9221 | ingestion | Meltano support for PEP 723 scripts | 1. What would it take for Meltano to run scripts with inline dependencies ([PEP 723](https://peps.python.org/pep-0723/))
2. What type use cases would this benefit? Maybe single-file taps?
## Example
This might look something like
```yaml
plugins:
extractors:
- name: tap-example
namespace: tap_exam... | [
"meltano"
] | false | [
"installation",
"plugin management"
] | meltano_errors | 0 | 0 | open | 2025-04-15T22:58:28Z | meltano/meltano | |
gh-disc-meltano-meltano-9169 | github_discussions | https://github.com/meltano/meltano/discussions/9169 | ingestion | v3.7.0 | ## v3.7.0 (2025-03-25)
### Highlights
This release brings several major enhancements including support for relative dates, custom state backends, and improved logging capabilities and user-friendliness.
#### Relative dates
Settings of [kind `date_iso8601`](https://docs.meltano.com/reference/plugin-definitio... | Some taps don't like us converting `Z`-suffixed datetimes to offset format, i.e. `+00:00`: https://github.com/meltano/meltano/issues/9172.
PR: https://github.com/meltano/meltano/pull/9173. | [
"json",
"meltano",
"gcs"
] | true | [] | meltano_errors | 0 | 1 | open | 2025-03-25T20:39:39Z | meltano/meltano |
gh-disc-meltano-meltano-9157 | github_discussions | https://github.com/meltano/meltano/discussions/9157 | ingestion | Installation failures causes by setuptools 78 | For some legacy plugins, mostly those based on https://github.com/singer-io/singer-python, users may start getting an installation error on Python 3.12+:
```
setuptools.errors.InvalidConfigError: Invalid dash-separated key 'description-file' in 'metadata' (setup.cfg), please use the underscore name 'description_fil... | I made a PR to try and fix this upstream in the package that is most likely to affect plugin installation https://github.com/singer-io/singer-python/pull/170. | [
"meltano"
] | false | [] | meltano_errors | 0 | 2 | open | 2025-03-24T17:04:08Z | meltano/meltano |
gh-disc-meltano-meltano-9068 | github_discussions | https://github.com/meltano/meltano/discussions/9068 | ingestion | Make `uv` the default venv backend | This also means
- [x] making a hard dependency on `uv`, which we could start with in the next release
- [x] then make the switch to the new default in a future release.
| > This also means making a hard dependency on `uv`
Other tools do this, so I guess having the tool be always available outweighs duplicating it in the same machine:
- [tox-uv](https://github.com/tox-dev/tox-uv/blob/99388233c6f164429accbf2333764a0fb14660d4/pyproject.toml#L46)
- [hatch](https://github.com/pypa/hat... | [
"meltano"
] | false | [
"installation",
"plugin management",
"dependencies"
] | meltano_errors | 0 | 2 | open | 2025-01-30T18:25:29Z | meltano/meltano |
gh-disc-meltano-meltano-8984 | github_discussions | https://github.com/meltano/meltano/discussions/8984 | ingestion | Custom Utilities and dbt Transforms Not Being Tracked in Meltano State | Hi Meltano team,
I’ve noticed that neither dbt transforms nor custom utilities (like calculate_free_slot:run_script) are being tracked in Meltano’s state database when included in a job.
For example, I have a job configured like this:
yaml
Copia codice
jobs:
- name: complete_elt
tasks:
- tap-mysql tar... | @mistermax80 the state db is only used for tracking incremental loading of data movement jobs. What sort of data are you wanting to track for utilities? cc @edgarrmondragon in case this was answered on Slack and can be closed. | [
"dbt",
"mysql",
"meltano",
"postgres"
] | true | [] | meltano_errors | 0 | 2 | open | 2024-12-28T08:32:59Z | meltano/meltano |
gh-disc-meltano-meltano-8854 | github_discussions | https://github.com/meltano/meltano/discussions/8854 | ingestion | Should we test Meltano against Amazon Linux? | Got some Meltano download data using [`pypinfo`](https://github.com/ofek/pypinfo).
```console
$ pypinfo --days 1 --limit 20 --percent --markdown "meltano" system distro pyversion
Served from cache: False
Data processed: 223.36 MiB
Data billed: 224.00 MiB
Estimated cost: $0.01
```
<details><summary>Download ... | FWIW here's the current support schedule:
```console
$ eol --md amazon-linux
```
| cycle | release | latest | latest release | support | eol | link |
| :-------| :--------: | :---------... | [
"meltano"
] | false | [] | meltano_errors | 0 | 1 | open | 2024-10-25T18:12:44Z | meltano/meltano |
gh-disc-meltano-meltano-8332 | github_discussions | https://github.com/meltano/meltano/discussions/8332 | ingestion | Meltano + Apache Spark? | Hi, I'm creating a custom loader that requires the use of pyspark, but given the template, I'm not sure how spark-submit would work with meltano?
If anyone has any experience with this and can shed some light on good approaches, I'd very much appreciate it! | [
"meltano",
"spark"
] | true | [] | meltano_errors | 0 | 0 | open | 2023-12-29T01:14:02Z | meltano/meltano | |
gh-disc-meltano-meltano-8331 | github_discussions | https://github.com/meltano/meltano/discussions/8331 | ingestion | `meltano install` not working inside a docker container | I'm trying to run a very simple test run of Meltano (tap-csv -> target-s3) locally using docker.
I was able to get this working fine outside of it, but inside the container, it keeps throwing this error:
```
Cannot start plugin tap-csv: Executable 'tap-csv' could not be found. Extractor 'tap-csv' may not have bee... | I'm not sure exactly how `meltano install` works, but turns out I need to run it in the production stage, not the build stage. Copying the venv and project files after running `meltano install` is not enough. | [
"s3",
"csv",
"meltano",
"docker"
] | true | [] | meltano_errors | 0 | 1 | answered | 2023-12-28T00:40:15Z | meltano/meltano |
gh-disc-meltano-meltano-8330 | github_discussions | https://github.com/meltano/meltano/discussions/8330 | ingestion | How to specify a different location for .env | Hi, I'm running a project that has more than just meltano and I'd like meltano.yml to be able to refer to environment variables (i.e. from `.env` file outside of the meltano project root).
Is there a way to accomplish this?
Thanks in advance for all your help! | Hi @seunggs! Currently Meltano will only look for a `.env` file in the directory that contains the `meltano.yml` file, so I think the only way to accomplish what you're asking for currently would be to add a symbolic link named `.env` within the directory containing `meltano.yml` that points to the real `.env` file.
... | [
"meltano"
] | false | [] | meltano_errors | 0 | 2 | answered | 2023-12-27T20:01:18Z | meltano/meltano |
gh-disc-meltano-meltano-8318 | github_discussions | https://github.com/meltano/meltano/discussions/8318 | ingestion | Regarding tap-s3 connector | Hi all,
I wanted to extract data from my s3 source but the catch is that data is in parquet format. I wanted to know what is the best way to extract it ? We only have tap-s3-csv connector available from official hub.
I could think of 2 approaches:
1. Create a new tap tap-s3-parquet and take care of decoding parquet ... | It may be a relatively low effort to support Parquet in https://github.com/MeltanoLabs/tap-universal-file | [
"s3",
"csv",
"parquet",
"json",
"meltano",
"postgres"
] | true | [] | meltano_errors | 0 | 1 | open | 2023-12-14T12:36:01Z | meltano/meltano |
gh-disc-meltano-meltano-8305 | github_discussions | https://github.com/meltano/meltano/discussions/8305 | ingestion | v3.2.0 | ## v3.2.0 (2023-12-05)
### ✨ New
- [#8184](https://github.com/meltano/meltano/issues/8184) Log Meltano version and Operating System at invocation of CLI -- _**Thanks @ashu565!**_
- [#8228](https://github.com/meltano/meltano/issues/8228) Support setting configuration from files and STDIN -- _**Thanks @XshubhamX... | [
"s3",
"meltano",
"dbt",
"azure"
] | true | [] | meltano_errors | 0 | 0 | open | 2023-12-05T19:27:44Z | meltano/meltano | |
gh-disc-meltano-meltano-8276 | github_discussions | https://github.com/meltano/meltano/discussions/8276 | ingestion | Custom state backends | I managed to stand up a [working feature branch of meltano](https://github.com/mjsqu/meltano/tree/feat/aws_ssm_state_backend) using AWS SSM Parameter Store as its state backend. The following state commands were analogous to the boto3 ssm client functions:
|meltano state ... command|ssm client function|
|---|---|
... | From: https://meltano.slack.com/archives/C013Z450LCD/p1700177112720099?thread_ts=1700118139.892419&cid=C013Z450LCD
(https://discuss.meltano.com/c/contributing - when the above Slack message expires) | [
"s3",
"meltano",
"azure"
] | true | [
"State Management"
] | meltano_errors | 0 | 2 | open | 2023-11-16T23:24:51Z | meltano/meltano |
gh-disc-meltano-meltano-7835 | github_discussions | https://github.com/meltano/meltano/discussions/7835 | ingestion | HuggingFace type interface | Random idea here:
I've been using https://huggingface.co/models a lot for data models and also wishing that something similar existed for ETL.
The Meltano hub is a great resource for me for finding taps however what doesn't exist yet and what I wish did exist is something Hugging Face for ETL. Specifically, if i... | @keithhackbarth thanks for opening the discussion.
One of the challenges with your request is that currently everything on the Hub is currently installable and usable with Meltano. The YAML definitions that power the site also power the API which Meltano queries to get the settings, configuration, and details on ho... | [
"meltano"
] | false | [] | meltano_errors | 0 | 1 | open | 2023-06-22T15:19:07Z | meltano/meltano |
gh-disc-meltano-meltano-7827 | github_discussions | https://github.com/meltano/meltano/discussions/7827 | ingestion | How (if at all) should Meltano Cloud leverage the Meltano system DB? | Follows from:
- https://github.com/meltano/infra/issues/1416#issuecomment-1601074219
My initial comment:
> Meltano core already uses mutexes to prevent the same schedule from running multiple times in parallel, but as @pnadolny13 called out:
>
>> but I think we've implemented cloud without a standard meltan... | From our office hours discussion and https://docs.meltano.com/concepts/project#system-database it sounds like the system db has these pieces of functionality:
1. State bookmark tracking
2. Tracking job history
3. Locking to disallow 2 jobs at the same time
4. User management
5. Settings management
Ideally we'... | [
"meltano"
] | false | [] | meltano_errors | 0 | 2 | open | 2023-06-21T16:09:26Z | meltano/meltano |
gh-disc-meltano-meltano-7809 | github_discussions | https://github.com/meltano/meltano/discussions/7809 | ingestion | Refactoring settings/config/environment variable management -- when and how? | Settings management and environment variable expansion has been a consistent pain point and source of bugs within meltano core. We've made some progress--particularly with regards to better testing and all the bugfixes done as part of the meltano manifest work--over the past year, but it's often one step forward and tw... | @cjohnhanson You and I have talked a fair bit about this topic, so you're already aware that I'm keen for us to tackle a refactor of how Meltano handles configuration for myriad reasons. The most concrete suggestion I've made to date on this topic is:
- https://github.com/meltano/meltano/issues/7400
In a nutshell, ... | [
"meltano"
] | false | [] | meltano_errors | 0 | 1 | open | 2023-06-15T20:47:00Z | meltano/meltano |
gh-disc-meltano-meltano-7684 | github_discussions | https://github.com/meltano/meltano/discussions/7684 | ingestion | Issue with Extractor Configuration in Meltano: Extractor Not Recognized During Testing | During my exploration of Meltano, I encountered an issue related to the configuration of CSV extractor. After configuring the extractor, I proceeded to test it, but unfortunately, Meltano displayed an error indicating that the extractor was not properly configured. In this discussion, I would like to share my experienc... | @manishlalwani0410 we'll need some more information to help you debug. What system are you running on, what's your meltano.yml look like (with sensitive information removed), what commands did you run? | [
"csv",
"meltano"
] | true | [] | meltano_errors | 0 | 3 | open | 2023-05-19T08:08:27Z | meltano/meltano |
gh-disc-meltano-meltano-9076 | github_discussions | https://github.com/meltano/meltano/discussions/9076 | ingestion | Avoid use of shell-processed characters such as `*` in CLI | Context:
- https://github.com/meltano/meltano/pull/7467#discussion_r1158588785
---
Currently `meltano state list` accepts a `--pattern` argument which can use `*` as a wildcard. Since most shells expand this character, it must be quoted. We have no way to enforce quotation of the argument, and no practical way t... | @WillDaSilva - We have a similar challenge with `meltano select`. In some cases, however ,they may not be a viable workaround with prefix/suffix/contains.
What do you think of accepting `'%'` as a replacement for `'*'` when wildcard behavior is still desirable? | [
"meltano"
] | false | [
"stale"
] | meltano_errors | 0 | 4 | open | 2023-04-05T14:55:04Z | meltano/meltano |
gh-disc-meltano-meltano-9057 | github_discussions | https://github.com/meltano/meltano/discussions/9057 | ingestion | Feature proposal: `meltano config validate` | This could also be invoked inline as part of `meltano test ...`.
We can also print inline as warnings:
1. Whenever a plugin is invoked.
2. After `meltano config set --interactive`.
3. During project linting (#7285)
Ideally these would also print requirements or explain requirements to users: `meltano config ... | My thoughts on this are also related to https://github.com/meltano/sdk/issues/1519, an issue about being able to know if an SDK plugin has valid settings based on user defined groups of settings.
If these groups of settings are in the SDK, and present in an SDK plugin when a user runs `meltano config set --interacti... | [
"meltano"
] | false | [
"cli"
] | meltano_errors | 0 | 3 | open | 2023-03-29T16:38:05Z | meltano/meltano |
gh-disc-meltano-meltano-9058 | github_discussions | https://github.com/meltano/meltano/discussions/9058 | ingestion | feat: when duplicate plugin found (different variant) automatically rename | From:
* https://github.com/meltano/meltano/issues/7392#issuecomment-1473961220
instead of failing we should try to succeed by renaming the plugin if the variant is different.
```bash
$ meltano add extractor tap-postgres --variant meltanolabs
Extractor 'tap-postgres' already exists in your Meltano project
... | This has been marked as stale because it is unassigned, and has not had recent activity. It will be closed after 21 days if no further activity occurs. If this should never go stale, please add the `evergreen` label, or request that it be added.
| [
"meltano",
"postgres"
] | true | [
"kind/Feature",
"valuestream/Meltano",
"stale"
] | meltano_errors | 0 | 3 | open | 2023-03-17T16:49:16Z | meltano/meltano |
gh-disc-meltano-meltano-7323 | github_discussions | https://github.com/meltano/meltano/discussions/7323 | ingestion | `meltano compile` feature, feedback and future changes | As of Meltano `v2.16`, we launched `meltano compile`, which generates a Manifest JSON file.
We are launching this in "beta" status and will be collecting feedback from community members and as we expect some changes as we incorporate feedback and usage data.
Users, community members, and third parties which want ... | [
"json",
"meltano"
] | true | [] | meltano_errors | 0 | 0 | open | 2023-02-16T00:18:42Z | meltano/meltano | |
gh-disc-meltano-meltano-7297 | github_discussions | https://github.com/meltano/meltano/discussions/7297 | ingestion | Discussion on options to pin Python package versions and manage python version bump lifecycles | Re:
- https://github.com/meltano/meltano/issues/6416
Currently we have lockfiles to lock plugin definitions, but those plugin definitions are most often using unpinned repo references and/or unpinned PyPi references.
Today, users are advised to manually add version constraints to the `pip_url` declaration in t... | One option that does not require changes to Meltano Core would be to run a periodic job on the Hub (perhaps mimicking what [HubCap](https://github.com/dbt-labs/hubcap) already does for dbt Hub), we could scrape versions and bump them from GitHub and/or PyPi. Then, all plugins on the hub would be pinned to specific Pyth... | [
"meltano",
"dbt"
] | true | [] | meltano_errors | 0 | 5 | open | 2023-02-09T18:59:32Z | meltano/meltano |
gh-disc-meltano-meltano-7257 | github_discussions | https://github.com/meltano/meltano/discussions/7257 | ingestion | What is the best way to run a Meltano pipeline in 1000 variations? | ## First challenge - how to invoke the same pipeline with 100 or 1000 different client connection strings or account numbers
The standard way to implement this as of today would be to declare a `state-id-suffix` in your environment definition, and use a unique string for each customer or each variation of the pipeli... | This is probably a bit of an aside, given it's not a wholly meltano solution, but might be of interest.
I think we could do this in our environment as of now, we run meltano via AWS ECS. We already run many Airflow tasks using the same connections, but split across multiple tasks to sync different sets of tables/end... | [
"meltano",
"airflow"
] | true | [] | meltano_errors | 0 | 1 | open | 2023-01-31T20:35:09Z | meltano/meltano |
gh-disc-meltano-meltano-7230 | github_discussions | https://github.com/meltano/meltano/discussions/7230 | ingestion | Consider a leaner Meltano Project scaffold | ```
aj@AJs-MacBook-Pro Source % meltano init test-project
Creating .meltano folder
created .meltano in /Users/aj/Source/test-project/.meltano
Creating project files...
test-project/
|-- meltano.yml
|-- README.md
|-- requirements.txt
|-- output/.gitignore
|-- .gitignore
|-- extract/.gitkee... | There's also the `plugins/` directory for lock files | [
"csv",
"airflow",
"json",
"meltano",
"dbt"
] | true | [] | meltano_errors | 0 | 3 | open | 2023-01-29T04:36:14Z | meltano/meltano |
gh-disc-meltano-meltano-7225 | github_discussions | https://github.com/meltano/meltano/discussions/7225 | ingestion | Does anyone know what the elt buffer size limit is? | What is the largest the elt.buffer_size can be set to? Would it be possible to set it to say 2GB? | @aaronsteers @edgarrmondragon do you all know? | [
"meltano"
] | false | [] | meltano_errors | 0 | 1 | open | 2023-01-26T23:50:31Z | meltano/meltano |
gh-disc-meltano-meltano-7192 | github_discussions | https://github.com/meltano/meltano/discussions/7192 | ingestion | Change from CLI-first to YAML-first Workflows | All documentation and most marketing material for Meltano so far advertise "CLI-first" workflow. Urging developers to run interactive configs, sequences of CLI commands and only default to editing the `meltano.yml` file if no other option is available.
I propose to exchange this order, advertising developers to use... | I've just finished configuring 49 taps that inherit from `tap-google-analytics`. I wrote a longer note in https://github.com/meltano/meltano/issues/7165#issuecomment-1396940667 but I think if I had done all the configuration of those plugins in YAML I'd have been more efficient. | [
"csv",
"meltano"
] | true | [] | meltano_errors | 0 | 5 | open | 2023-01-19T12:38:30Z | meltano/meltano |
gh-disc-meltano-meltano-7153 | github_discussions | https://github.com/meltano/meltano/discussions/7153 | ingestion | Consider replacement of Make and Makefile | In this PR
- https://github.com/meltano/meltano/pull/6488
We removed Makefile. I'm opening this discussion to explore what (if anything) might replace that in the future.
Some options we discussed in our Codeshare meeting today (Jan 5, 2022):
- Option 1: Don't replace. (Rely on Contributing docs and/or CI w... | @aaronsteers I didn't notice that, I was quite happy to have a "build docs" command inside make, so I'll offer an opinion.
IMHO for open-source projects it is even more important than for "traditional in-house development" to have super quick setup 6 dev functionalities for new/existing contributors (https://www.tho... | [
"meltano",
"docker"
] | true | [] | meltano_errors | 0 | 3 | open | 2023-01-06T05:51:42Z | meltano/meltano |
gh-disc-meltano-meltano-7142 | github_discussions | https://github.com/meltano/meltano/discussions/7142 | ingestion | Airbyte Source Connector support with Meltano | A fantastic community member added support for Airbyte connectors within Meltano. This dicussion can be used to answer any questions or provide any feedback on the integration.
* [tap-airbyte-wrapper](https://github.com/MeltanoLabs/tap-airbyte-wrapper) on GitHub
* [FAQ](https://docs.meltano.com/guide/advanced-topic... | Hi,
Did someone succed to use tap-airbyte-wrapper with docker-compose ?
I tried to with custom build with meltano and docker.io
I was able to run `docker ps` in the container, but when i tried with tap-sonar-cloud i've got : `No such file or directory: '/tmp/config.json'` | [
"json",
"meltano",
"docker"
] | true | [] | meltano_errors | 0 | 1 | open | 2023-01-03T17:09:32Z | meltano/meltano |
gh-disc-meltano-meltano-7137 | github_discussions | https://github.com/meltano/meltano/discussions/7137 | ingestion | Discuss: CLI syntax sometimes requires subcommands to be named after project-specific predicates | The general best practice for CLI subcommands is
```
cli-exec COMMAND SUBCOMMAND --option-a=val --flag-b
```
However, Meltano's CLI often requires the object of the command to be specified _before_ the subcommand is called.
For instance, we have:
```
meltano config my-plugin set SETTING VALUE
```
Wh... | @aaronsteers I'm in favor of this. It aligns with our contributor guide https://docs.meltano.com/contribute/cli and also follows the implementation we've had for many of our more recent commands:
```bash
meltano schedule set <schedule_name> --job <new-job>
meltano job set <job_name> --tasks
meltano environmen... | [
"meltano"
] | false | [] | meltano_errors | 0 | 1 | open | 2022-12-28T01:26:07Z | meltano/meltano |
gh-disc-meltano-meltano-7100 | github_discussions | https://github.com/meltano/meltano/discussions/7100 | ingestion | Spec discussion: Meltano "modules" as fully-functional sub-projects | Based on the prior discussions in:
- https://github.com/meltano/meltano/issues/6678
- https://github.com/meltano/hub/issues/210
## Spec draft status
This is a very early and speculative draft. It draws upon prior conversations and thought work from this topic, but it is not intended to be final or authoritati... | [
"meltano",
"snowflake"
] | true | [] | meltano_errors | 0 | 0 | open | 2022-12-16T07:35:36Z | meltano/meltano | |
gh-disc-meltano-meltano-7086 | github_discussions | https://github.com/meltano/meltano/discussions/7086 | ingestion | Meltano HackDay project ideas: April 14 2023 | Opening this discussion to explore project ideas for our Jan 2023 HackDay event:
- https://github.com/meltano/internal-general/issues/461 | A few ideas:
- A tutorial for exporting and visualizing Singer metrics in a time-series database like InfluxDB
- A PoC for the Hub API built on top of FastAPI
- `singer-rust` PoC and build a simple tap or target, publish a Python wheel
- ~A node wrapper for npm plugins that uses https://pypi.org/project/nodejs-bi... | [
"meltano"
] | false | [] | meltano_errors | 0 | 3 | open | 2022-12-14T05:57:30Z | meltano/meltano |
gh-disc-meltano-meltano-7056 | github_discussions | https://github.com/meltano/meltano/discussions/7056 | ingestion | Spec discussion: allow pointers in yaml to reference settings values in other stores | Part of a multi-part set of feature releases:
1. https://github.com/meltano/meltano/discussions/6999
1. https://github.com/meltano/meltano/discussions/7055
1. https://github.com/meltano/meltano/discussions/7056 (this item)
It would be good to have ability to place pointers to specific settings into our yaml fil... | I like this! It would allow a project to be really explicit about where it expects settings to be coming from:
Wdyt of the syntax:
```yaml
plugins:
extractors:
- name: my-tap
config:
token: cfg://envvar/MY_TAP_TOKEN?dotenv=true
```
I recently saw a similar syntax in Python's logging config:... | [
"meltano"
] | false | [] | meltano_errors | 0 | 2 | open | 2022-12-06T21:26:32Z | meltano/meltano |
gh-disc-meltano-meltano-7055 | github_discussions | https://github.com/meltano/meltano/discussions/7055 | ingestion | Spec discussion: Meltano Cloud as an alternative config store backends | Part of a multi-part set of feature releases:
1. https://github.com/meltano/meltano/discussions/6999
1. https://github.com/meltano/meltano/discussions/7055 _(this item)_
1. https://github.com/meltano/meltano/discussions/7056
----------------------
```yaml
secrets_config:
# keys: []
# encryption_key: ... | [
"meltano"
] | false | [] | meltano_errors | 0 | 0 | open | 2022-12-06T21:21:04Z | meltano/meltano | |
gh-disc-meltano-meltano-7053 | github_discussions | https://github.com/meltano/meltano/discussions/7053 | ingestion | Allowing vendor-specific annotations in `meltano.yml` | We want to allow vendor-specific annotations for `meltano.yml` files. As of today, users can add extra nodes to the file, and these _probably_ won't break anything - but there is no officially sanctioned key to use for annotations.
This proposal would reserve a specific key ID for annotations, which would have the f... | I'm a big fan of `meta` for clear reasons https://github.com/dbt-labs/dbt-core/pull/2015 😄 | [
"json",
"meltano",
"dbt",
"airflow"
] | true | [] | meltano_errors | 0 | 4 | open | 2022-12-06T18:19:32Z | meltano/meltano |
gh-disc-meltano-meltano-7016 | github_discussions | https://github.com/meltano/meltano/discussions/7016 | ingestion | Improve readability of Meltano's console output | Starting this discussion to scope out work that would improve the 'default' user experience when running Meltano.
Related:
- https://github.com/meltano/meltano/discussions/6642#discussioncomment-3448447
A few changes I'll propose for a start, and folks can chime in with comments below for other ideas/proposal... | @tayloramurphy, @pnadolny13, @sbalnojan - I've taken several rounds of iteration on the above and would love feedback/discussion on these points.
The above is very detailed so here is the per-line-item summary:
1. **Enable file logging by default.** This helps users debug, but it also removes the need for console... | [
"meltano"
] | false | [] | meltano_errors | 0 | 4 | open | 2022-11-22T22:25:02Z | meltano/meltano |
gh-disc-meltano-meltano-6999 | github_discussions | https://github.com/meltano/meltano/discussions/6999 | ingestion | Spec for `meltano config` support for encryption | Part of a multi-part set of feature releases:
1. https://github.com/meltano/meltano/discussions/6999 _(this item)_
- 1. https://github.com/meltano/meltano/issues/6987
1. https://github.com/meltano/meltano/discussions/7055
1. https://github.com/meltano/meltano/discussions/7056
----------------------
The... | @aaronsteers I've updated the spec based on our conversation in Slack
| [
"meltano"
] | false | [] | meltano_errors | 0 | 4 | open | 2022-11-17T03:14:27Z | meltano/meltano |
gh-disc-meltano-meltano-6993 | github_discussions | https://github.com/meltano/meltano/discussions/6993 | ingestion | v2.10.0 | ## v2.10.0 (2022-11-16)
### ✨ New
- [#6911](https://github.com/meltano/meltano/issues/6911) Add support for [state backends](https://docs.meltano.com/concepts/state_backends) in S3, Google Cloud Storage, Azure Blob Storage, and local filesystem.
### 🐛 Fixes
- [#6971](https://github.com/meltano/meltano/issu... | [
"s3",
"meltano",
"gcs",
"azure"
] | true | [] | meltano_errors | 0 | 0 | open | 2022-11-16T07:33:08Z | meltano/meltano | |
gh-disc-meltano-meltano-6967 | github_discussions | https://github.com/meltano/meltano/discussions/6967 | ingestion | Meltano v2.9.0 | ## Meltano v2.9.0 (2022-11-08)
### ✨ New
- [#6964](https://github.com/meltano/meltano/issues/6964) Add `--cwd` CLI option to override the current working directory.
- [#6785](https://github.com/meltano/meltano/issues/6785) Add support for `NO_COLOR` env var to disable colored output.
- [#6628](https://github.co... | [
"meltano"
] | false | [] | meltano_errors | 0 | 0 | open | 2022-11-08T05:17:52Z | meltano/meltano | |
gh-disc-meltano-meltano-6957 | github_discussions | https://github.com/meltano/meltano/discussions/6957 | ingestion | Future Meltano UI Features and Functionality | This is a general discussion around what features and functionality people would like to see in the Meltano UI.
View this PR for more context:
* https://github.com/meltano/meltano/pull/6955 | [
"meltano"
] | false | [] | meltano_errors | 0 | 0 | open | 2022-11-03T19:15:45Z | meltano/meltano | |
gh-disc-meltano-meltano-6952 | github_discussions | https://github.com/meltano/meltano/discussions/6952 | ingestion | Future features discussion: Additional/alternative state backends | Drop a comment here if you have suggestions.
Related to:
- #6911 | I've heard a few people in slack ask about a snowflake state backend to simplify infrastructure if they dont want a standalone OLTP db or S3/GCP/Azure bucket and already need Snowflake.
- https://meltano.slack.com/archives/C01UTUSP34M/p1661967818591489
- https://meltano.slack.com/archives/C01TCRBBJD7/p1649967936914... | [
"s3",
"meltano",
"azure",
"snowflake"
] | true | [] | meltano_errors | 0 | 1 | open | 2022-11-02T16:43:49Z | meltano/meltano |
gh-disc-meltano-meltano-6950 | github_discussions | https://github.com/meltano/meltano/discussions/6950 | ingestion | docs: Consider using sqlite over postgres in getting started guides | Related to https://github.com/meltano/internal-data/issues/39#issuecomment-1297715601 (private) and https://github.com/meltano/internal-data/issues/38#issuecomment-1297723663 (private).
When digging into what new users are doing we see high usage of tap and target postgres. As part of that we see a fair amount of fa... | @pnadolny13 Maybe, to get people to first run that will help.
But I'm a bit torn on this subject as I think it's of high importance to provide a great tap & target postgres. So instead (or decoupled from this) we could prioritize work on the high quality taps & targets that just work.
I think it's always a fine... | [
"docker",
"meltano",
"postgres"
] | true | [] | meltano_errors | 0 | 2 | open | 2022-11-01T14:59:13Z | meltano/meltano |
gh-disc-meltano-meltano-6949 | github_discussions | https://github.com/meltano/meltano/discussions/6949 | ingestion | Path to a Meltano Python library | Opening this discussion to start charting a path towards a public Python API for Meltano.
Key questions:
1. Should `meltano/meltano` become a mono-repo containing `meltano` and `meltano-core` as separate PyPi packages?
2. If 'yes' to the above, do we need to introduce new monorepo CI orchestration tools to assis... | Things that we could/should split early:
- Anything to do with plugin definition:
- `PluginType` enum
- `SettingDefinition` and all its fields (`SettingKind`, etc.)
- `Command`
- etc.
This would help at least with decoupling a Hub API from the Hub site, and generate schemas for all these structs i... | [
"meltano"
] | false | [] | meltano_errors | 0 | 1 | open | 2022-11-01T03:48:59Z | meltano/meltano |
gh-disc-meltano-meltano-6944 | github_discussions | https://github.com/meltano/meltano/discussions/6944 | ingestion | Spec discussion: UX for creating Meltano's `manifest.json`? | We're wanting to build out the Meltano manifest sooner than later, as as an enabling feature for Managed interop:
- #6876
## CLI Proposal
`meltano [--environment=ENVIRONMENT] compile [--output=OUTPUT_FILE]`
## Output proposal
1. If `--environment` is provided, compile a manifest file that fully describe... | @aaronsteers at first glance this seems ok but a question comes up for me. Does each file get the global / non-environment compilation with it as well, or is that a separate file?
```
/.meltano/complied/
global.json
dev.json
prod.json
```
Something like that?
Also, for this first iteration, does it ... | [
"json",
"meltano"
] | true | [] | meltano_errors | 0 | 2 | open | 2022-10-28T17:14:30Z | meltano/meltano |
gh-disc-meltano-meltano-6909 | github_discussions | https://github.com/meltano/meltano/discussions/6909 | ingestion | v2.8.0 | ## v2.8.0 (2022-10-17)
### ✨ New
- [#6814](https://github.com/meltano/meltano/pull/6814) Support [`meltano init`](https://docs.meltano.com/reference/command-line-interface#init) into an empty directory -- _**Thanks @ReubenFrankel!**_
### 🐛 Fixes
- [#6751](https://github.com/meltano/meltano/issues/6751) Re... | [
"meltano"
] | false | [] | meltano_errors | 0 | 0 | open | 2022-10-18T13:15:06Z | meltano/meltano | |
gh-disc-meltano-meltano-6886 | github_discussions | https://github.com/meltano/meltano/discussions/6886 | ingestion | Should we support encrypted key values in yaml, in the style of Mozzila `Sops` or Ansible `Vault` | Competing/alternate proposal:
- https://github.com/meltano/meltano/discussions/6879
Reference:
- https://github.com/mozilla/sops#sops-secrets-operations
- https://docs.ansible.com/ansible/latest/user_guide/vault.html
General proposal and challenges:
1. The Managed infra would still need to manage a set ... | Replaced by:
- #6999 | [
"meltano"
] | false | [] | meltano_errors | 0 | 1 | answered | 2022-10-13T22:43:20Z | meltano/meltano |
gh-disc-meltano-meltano-6879 | github_discussions | https://github.com/meltano/meltano/discussions/6879 | ingestion | New paradigm for secrets as key-value env var mappings, abstracted from settings | Competing/alternate proposal:
- https://github.com/meltano/meltano/discussions/6886
## Prior thinking
We've been roughly categorizing 'secrets' as a subset of plugin 'config' values. This is problematic for a few different reasons, for instance:
1. It's not very DRY if defined at the plugin setting level.
... | @aaronsteers much of this proposal I think is encapsulated in:
* https://github.com/meltano/meltano/issues/3276
It's not clear to me what you're proposing here that would be too different from that issue. It seems like you're proposing a more generic form of `connections` (namely `secrets`) that can be a write on... | [
"meltano",
"docker",
"snowflake"
] | true | [] | meltano_errors | 0 | 3 | open | 2022-10-12T23:42:19Z | meltano/meltano |
gh-disc-meltano-meltano-6850 | github_discussions | https://github.com/meltano/meltano/discussions/6850 | ingestion | Spec discussion: new `meltano log` CLI | We would love to have a `logging` feature accessible via the CLI.
### `meltano log list` (raw list of executions)
List all the available logs (up to max count 'n'). Log list can be filtered by schedule name, job name, plugin name, or state ID.
```
meltano log list [PLUGIN_NAME|SCHEDULE_NAME|JOB_NAME|STATE_I... | @aaronsteers Apologies for the delayed response here.
> meltano log summary
In thinking more on this one, I'm less a fan because it's trying to do too much.
`Would show a summary of all job and schedule names which have executed over the specified local period.`
I'd rather we add more to `meltano log list`... | [
"s3",
"json",
"meltano"
] | true | [] | meltano_errors | 0 | 2 | open | 2022-10-04T22:29:50Z | meltano/meltano |
gh-disc-meltano-meltano-9112 | github_discussions | https://github.com/meltano/meltano/discussions/9112 | ingestion | feat: support Environment 'extras' | Following this comment on [env var expansion](https://github.com/meltano/meltano/pull/6758#discussion_r977547766), it strikes me that manual expansion is needed in this case because `state_id_suffix` is implemented as a new attribute of the `Environment`, and so bypasses the `get`/`get_with_metadata` method on the `Set... | This has been marked as stale because it is unassigned, and has not had recent activity. It will be closed after 21 days if no further activity occurs. If this should never go stale, please add the `evergreen` label, or request that it be added.
| [
"meltano"
] | false | [
"kind/Feature",
"kind/Tech Debt",
"valuestream/Meltano",
"env var"
] | meltano_errors | 0 | 5 | open | 2022-09-22T17:16:16Z | meltano/meltano |
gh-disc-meltano-meltano-6766 | github_discussions | https://github.com/meltano/meltano/discussions/6766 | ingestion | Spec Exploration for `meltano catalog` UX | Following from
- https://github.com/meltano/meltano/discussions/6757
I wanted to explore what a `meltano catalog` CLI command group might look like from a UX perspective.
Two fundamental use cases as I can see:
## Use case 1: Maintaining behind-the-scenes internal catalog artifacts
E.g.:
- `meltano ca... | I've made a milestone to gather many of the catalog related issues: https://github.com/meltano/meltano/milestone/12
With our refocus on EL it's going to be more important that we get the experience around the catalog, state, and mappers right as they're "must haves" and competitive advantages.
https://github.com... | [
"json",
"meltano",
"dbt",
"snowflake"
] | true | [] | meltano_errors | 0 | 3 | open | 2022-09-16T23:55:28Z | meltano/meltano |
gh-disc-meltano-meltano-6757 | github_discussions | https://github.com/meltano/meltano/discussions/6757 | ingestion | Spec discussion: Give users better control of catalog caching for taps | As raised here:
- https://github.com/meltano/meltano/issues/2848
- And [in slack](https://meltano.slack.com/archives/CKHP6G5V4/p1663216549001279?thread_ts=1663205560.565299&cid=CKHP6G5V4)
## Requirement overview
Some taps generate volatile schema, where the upstream source cannot be considered a closed system... | ## Option 1: Explicitly forcing the refresh of a catalog
A new `catalog` command with the subcommand `update` (or `refresh`, or similar) could explicitly rerun discovery.
```
# refresh the specific extractor's catalog before running EL
meltano catalog update tap-name
meltano run tap-name target-name
```
Or... | [
"meltano"
] | false | [] | meltano_errors | 0 | 4 | open | 2022-09-15T04:19:55Z | meltano/meltano |
gh-disc-meltano-meltano-6738 | github_discussions | https://github.com/meltano/meltano/discussions/6738 | ingestion | Docs Restructuring | I feel the documentation for Meltano could benefit from a restructuring, and I would love to hear community comments on this one because the goal is:
1. to get Meltano first timers onboarded as quickly as possible onto their first productionized pipeline
2. to get advanced users help quickly, or at least find "hole... | - Search on the main meltano site should either index docs, or make it very clear you need to go do docs.meltano.com to get the docs for Meltano
- How to guide idea: "How to find out if it's the tap, target, or meltano". (Ideally meltano would make this easier over time as well, but right now this takes some significa... | [
"meltano"
] | false | [] | meltano_errors | 0 | 3 | open | 2022-09-12T11:14:27Z | meltano/meltano |
gh-disc-meltano-meltano-6700 | github_discussions | https://github.com/meltano/meltano/discussions/6700 | ingestion | Spec discussion: Exception and Error Handling in Meltano | Opening this new discussion to come to a global set of standards for how we want to handle exceptions and errors within Meltano.
For this discussion (until another proposal is raised):
- Exceptions are things we may or may not handle up the call stack from where they occurred.
- Errors are things that will almos... | To start off the conversation, some steps we could start tackling:
1. [ ] Deliver #6640 and hopefully improve the printing of uncaught exceptions.
1. [ ] Confirm if #6640 on its own address/improves the situation in #6684.
1. [ ] Add to our dev standards some guidance on how to handle "Errors": what to print, how ... | [
"meltano"
] | false | [] | meltano_errors | 0 | 5 | open | 2022-09-01T19:42:14Z | meltano/meltano |
gh-disc-meltano-meltano-6687 | github_discussions | https://github.com/meltano/meltano/discussions/6687 | ingestion | Hacktoberfest 2022 | How should we handle [Hacktoberfest 2022](https://hacktoberfest.digitalocean.com/)? It's a month-long event ran by Digital Ocean wherein people are incentivized to create & merge PRs in public GitHub repositories. It has traditionally attracted a large amount of low-quality contributions.
Because of the low-quality ... | @WillDaSilva I think your proposal makes sense to me. We're not looking for just any random contribution. FYI @afolson since this is a consideration! | [
"meltano"
] | false | [] | meltano_errors | 0 | 1 | open | 2022-08-30T17:31:56Z | meltano/meltano |
gh-disc-meltano-meltano-6642 | github_discussions | https://github.com/meltano/meltano/discussions/6642 | ingestion | what is our cohesive logging and output UX experience | Opened this to discuss and document what our goals are for the user experience on the command line. Triggered by discussion in https://github.com/meltano/meltano/pull/6103
The command line should be offer completely functionality for working with your Meltano project, it should be nice to use, and it shouldn't try t... | @meltano/engineering @pnadolny13 would love your opinions on guiding principles around CLI output and UX. | [
"meltano"
] | false | [] | meltano_errors | 0 | 3 | open | 2022-08-17T21:47:49Z | meltano/meltano |
gh-disc-meltano-meltano-6639 | github_discussions | https://github.com/meltano/meltano/discussions/6639 | ingestion | How will mappers work with BATCH messaging? | SDK discussion link:
- https://github.com/meltano/sdk/issues/1117
One concern I brought up with @aaronsteers today was how stream maps will work with the `BATCH` message type.
My desired end state is that a mapper built on the SDK works with batch workflows out of the box no problem.
A worst case scenario... | @tayloramurphy
> Do we know if SDK-based stream maps will work out of the box?
Not really. For dumping batches of records from an API that's already returning individual records, which the SDK can simply _convert_ into a batch file, streams maps configured for the tap (e.g. `{"token": ..., "stream_maps": {...}}`... | [
"s3",
"csv",
"json",
"meltano",
"gcs"
] | true | [] | meltano_errors | 0 | 2 | open | 2022-08-16T21:23:58Z | meltano/meltano |
gh-disc-meltano-meltano-6617 | github_discussions | https://github.com/meltano/meltano/discussions/6617 | ingestion | Analyzing system-level dependencies for Postgres connectivity | In office hours, we discussed that our new slimmer and more secure docker images do not have full support for Postgres connectivity in some cases.
I did a quick scan of repos and all of these are using psycopg2-binary:
- [Meltano itself](https://github.com/meltano/meltano/blob/main/pyproject.toml#L52)
- [pipelinew... | Looks like this was expected to have been resolved in a prior Meltano release:
- [GitLab !1676 - Require `psycopg2-binary` instead of `psycopg2` so that build dependency `pg_config` doesn't need to be present on system](https://gitlab.com/meltano/meltano/-/merge_requests/1676)
| [
"docker",
"meltano",
"postgres"
] | true | [] | meltano_errors | 0 | 4 | open | 2022-08-12T16:53:43Z | meltano/meltano |
gh-disc-meltano-meltano-6595 | github_discussions | https://github.com/meltano/meltano/discussions/6595 | ingestion | Spec discussion: Interface to show running jobs, kill jobs, and print job logs | This is going to be multiple iterations, but each of these plays into the others:
1. How does meltano track what jobs are running (or thought to be running)?
- Can be based on either a process list print or a log file "start event" with recent-enough keepalive ping.
2. Based on `1`, we would create an ability f... | [
"meltano"
] | false | [] | meltano_errors | 0 | 0 | open | 2022-08-09T03:41:23Z | meltano/meltano | |
gh-disc-meltano-meltano-6571 | github_discussions | https://github.com/meltano/meltano/discussions/6571 | ingestion | Would we consider running benchmarks for common Tap/Target combos? | In an effort to i) better inform Tap/Target users on the Hub and ii) better track and celebrate improvements to Tap/Target performance, would it be feasible to run and publish benchmark figures for common Tap/Target pairs (e.g. Postgres to Snowflake)?
Some thoughts:
- Benchmarks likely only need to run monthly or a... | @kgpayne in general I like the idea! Anything we can do to show the quality of specific connectors I think would be good. We'd be somewhat limited by access to systems with representative data, but perhaps with our managed offering we could get some of that data. | [
"meltano",
"postgres",
"snowflake"
] | true | [] | meltano_errors | 0 | 1 | open | 2022-08-05T10:54:39Z | meltano/meltano |
gh-disc-meltano-meltano-6561 | github_discussions | https://github.com/meltano/meltano/discussions/6561 | ingestion | proposal: rename plugins to components with sub-categories of connectors, tools, and resources | Previously discussed in https://github.com/meltano/internal-general/issues/333 (private repo).
Proposal is to have a broad renaming of `plugins` --> `components`. A sub-category from there could potentially be `connectors`, `tools` and `resources`.
@aaronsteers proposed a few "frames" which we can use to evaluate... | > How we bucket or categorize plugins on hub.meltano.com.
Components would essentially be a drop-in replacement for plugins. Airflow, dbt, etc are components of your data stack.
> What appears in yaml to replace plugins: entry. (Another top-level entry or the new subcategories.)
I'm partial to dropping the top... | [
"meltano",
"dbt",
"airflow"
] | true | [
"kind/Feature",
"valuestream/Meltano"
] | meltano_errors | 0 | 3 | open | 2022-08-03T15:25:10Z | meltano/meltano |
gh-disc-meltano-meltano-6559 | github_discussions | https://github.com/meltano/meltano/discussions/6559 | ingestion | Should we be supporting dynamic DAG generation in Prod? | Should we be supporting dynamic DAG generator in production?
The way that the airflow DAG generator works right now requires that we are constantly running cli commands and asking meltano for a list of schedules/jobs which has pros and cons.
- Pro: allow users to edit crons or other attributes of schedules in pro... | @pnadolny13 thanks for bringing this up.
I'm inclined to say no we shouldn't allow changes to DAGs and their schedules in production. In this case, I think the read-only mode of the UI makes sense when the production deployment is activated. If users want to make a change, then they could enter an editing mode and ... | [
"kubernetes",
"meltano",
"dbt",
"airflow"
] | true | [] | meltano_errors | 0 | 1 | open | 2022-08-03T14:52:19Z | meltano/meltano |
gh-disc-meltano-meltano-6475 | github_discussions | https://github.com/meltano/meltano/discussions/6475 | ingestion | Are 'weekly' Meltano releases too frequent? | Our philosophy at Meltano has always been to release features to our users as soon as they are ready. This means we often have a 3 or 4 releases every month, which some users may have a hard time keeping up with.
Should we move to monthly releases, with only patch/hotfix updates in between our monthly cadence?
A... | > 🚀 Same as today! Release as soon as the features are ready!
Just wanna point out that what we do today is slight different than "release as soon as features are ready" which sorta implies a "release on merge" pattern. Our weekly release cadence is fast enough though that practically speaking it's basically the s... | [
"meltano"
] | false | [] | meltano_errors | 0 | 2 | open | 2022-07-25T17:10:38Z | meltano/meltano |
gh-disc-meltano-meltano-6459 | github_discussions | https://github.com/meltano/meltano/discussions/6459 | ingestion | Spec discussion: Should plugins support a top level `container_spec`? | We considered supporting a plugin-level `container_spec` option when we released the `container_spec` feature. The two reasons we declined a plugin-level `container_spec` at the time were:
## Challenge 1. Problematic UX around inheritance between the plugin and its commands.
There are a number of confusing and di... | [
"meltano"
] | false | [] | meltano_errors | 0 | 0 | open | 2022-07-21T00:59:50Z | meltano/meltano | |
gh-disc-meltano-meltano-6445 | github_discussions | https://github.com/meltano/meltano/discussions/6445 | ingestion | Spec discussion: Updating or freezing pip URL when running `lock --update` | There are approximately four ways we can pin a `pip_url` ref.
## Pip pin methods
### 1.A. Default branch pin
This is a pin to the repo itself. Whatever the default branch is, that branch's latest commit will be used during installation.
### 1.B. Pin to a named branch
The named branch would be used instea... | [
"meltano"
] | false | [] | meltano_errors | 0 | 0 | open | 2022-07-18T21:43:34Z | meltano/meltano | |
gh-disc-meltano-meltano-6441 | github_discussions | https://github.com/meltano/meltano/discussions/6441 | ingestion | Feature Idea: CLI `--cleanup=false` option to retain temp config files after execution | We currently have `--dump` options to unload config files. Another approach would be to offer a `--cleanup=false` option that performs the following functions:
1. Run all operations as usual.
2. Skip cleanup/purge of interim config files.
3. Print a message at end of execution which files were _not_ deleted so the... | @aaronsteers I really like the idea. Some thoughts:
- what does the team think of a simple boolean flag instead of a specified value? i.e. `--no-cleanup`
- I kinda wish we could extend `meltano remove` to make the plugin type and name optional, and so have a `--temp-files` flag to remove all catalog, config or othe... | [
"meltano"
] | false | [] | meltano_errors | 0 | 2 | open | 2022-07-18T19:32:20Z | meltano/meltano |
gh-disc-meltano-meltano-6388 | github_discussions | https://github.com/meltano/meltano/discussions/6388 | ingestion | Leverage a single logging config convention across Meltano and also SDK based taps/targets | Meltano has documented how to create a custom logging config file here: https://docs.meltano.com/reference/settings#clilog_config
This leverages a built-in python config file spec, along with specific class names and/or formatting settings.
Can we combine this with SDK conventions so that the same file can be use... | [
"meltano"
] | false | [] | meltano_errors | 0 | 0 | open | 2022-07-08T16:54:19Z | meltano/meltano | |
gh-disc-meltano-meltano-6374 | github_discussions | https://github.com/meltano/meltano/discussions/6374 | ingestion | Integration test backlog | Now that we have an integration test framework in place I thought it might be good to start a discussion around what all tests we should have. I figured recent additions are probably a good jumping off point so I've compiled some test candidates based on modifications made in 2.0 and forward.
1. meltano add & remove... | I just added an integration for https://github.com/meltano/meltano/pull/6308 | [
"meltano"
] | false | [] | meltano_errors | 0 | 1 | open | 2022-07-06T19:01:08Z | meltano/meltano |
gh-disc-meltano-meltano-6362 | github_discussions | https://github.com/meltano/meltano/discussions/6362 | ingestion | Meltano installation within docker container running airflow | I wanted to check if this has been tried before and if not what approach the community would suggest:
I have airflow running as docker containers and wanted to install meltano inside these containers so that most of my taps and targets would be available.
Any ideas around this ? | [
"meltano",
"docker",
"airflow"
] | true | [] | meltano_errors | 0 | 0 | open | 2022-07-06T09:28:43Z | meltano/meltano | |
gh-disc-meltano-meltano-6313 | github_discussions | https://github.com/meltano/meltano/discussions/6313 | ingestion | Consider adding internal architecture docs | We've had this discussion a few times, most recently (i think) in - https://gitlab.com/meltano/meltano/-/issues/3285 and https://gitlab.com/meltano/meltano/-/issues/3208#note_838070803. But I still think it would be pretty useful to have some internal architecture docs.
I think this part of my comment mostly still ... | [
"meltano"
] | false | [] | meltano_errors | 0 | 0 | open | 2022-06-29T15:01:28Z | meltano/meltano | |
gh-disc-meltano-meltano-6273 | github_discussions | https://github.com/meltano/meltano/discussions/6273 | ingestion | Future of `meltano elt` or `meltano el` (adapt vs deprecate) | Opening this discussion to explore use cases that might justify a version of `meltano elt` having ongoing support, versus phasing this out in favor of `meltano run`.
Related:
- https://github.com/meltano/meltano/issues/5940
- https://github.com/meltano/meltano/issues/6164
## Option A - Rename `elt` to `meltano... | @aaronsteers This recently came up in https://github.com/meltano/meltano/issues/6272#issuecomment-1165872738 and spawned https://github.com/meltano/meltano/issues/6289 as well.
For sure I don't think we're going to do any deprecations until 3.0. So with that assumption we'll need to continue to support it for now. ... | [
"meltano"
] | false | [] | meltano_errors | 0 | 2 | open | 2022-06-23T16:45:54Z | meltano/meltano |
gh-disc-meltano-meltano-6270 | github_discussions | https://github.com/meltano/meltano/discussions/6270 | ingestion | Spec discussion: Config layer and CLI interface for alternate state backends | In order to prepare for
- #5981
we will need to decide on a yaml and CLI spec for the state backend.
Functional requirements
1. The state backend will need to be configurable per environment.
1. The state backend does not necessarily need to be configured for the `--no-environment` case. (Okay either way... | @aaronsteers Note that making `state_backend` a top-level Meltano setting will not allow environment-specific overrides anymore once https://github.com/meltano/meltano/issues/6247 is done. | [
"s3",
"meltano"
] | true | [] | meltano_errors | 0 | 3 | open | 2022-06-22T20:56:34Z | meltano/meltano |
gh-disc-meltano-meltano-6256 | github_discussions | https://github.com/meltano/meltano/discussions/6256 | ingestion | `meltano elt` plugins_context on starting event | Related to https://github.com/meltano/meltano/pull/6068
It looks like the `meltano elt` telemetry event does get the plugin context but it attaches it to the final event (i.e. completed), for `meltano invoke` we get it as part of the first event (i.e. started). I remember invoke originally having it as the final eve... | Attaching plugin contexts to start events is actually not going to work anymore when we switch to firing an automatic "start" events (because at that stage we don't know anything about the plugins that will eventually be used).
So, we'll either need to attach them to final events or create a special event to fire w... | [
"meltano"
] | false | [
"Telemetry"
] | meltano_errors | 0 | 1 | open | 2022-06-21T20:38:53Z | meltano/meltano |
End of preview. Expand in Data Studio
README.md exists but content is empty.
- Downloads last month
- 7