Edgar Ramírez Mondragón

feat: Compute target metrics

3

### Feature scope Targets ### Description We have a few metrics computed for taps: * Record counter * Request counter * Sync timer * Request timer It would be interesting...

feat: Support nested replication keys

1

### Feature scope Taps (catalog, state, stream maps, etc.) ### Description ### Proposal #### Option 1 Use a JSONPath expression to declare the possibly nested field: ```python class MyStream(Stream): replication_key...

### Singer SDK Version 0.31.1 ### Is this a regression? - [ ] Yes ### Python Version NA ### Bug scope Mapping (stream maps, flattening, etc.) ### Operating System NA...

bug: Mapping crashing with empty stream

1

### Singer SDK Version 0.31.1 ### Is this a regression? - [ ] Yes ### Python Version NA ### Bug scope Mapping (stream maps, flattening, etc.) ### Operating System NA...

feat: Track memory usage in targets and drain record batch if a treshold is passed

2

### Feature scope Targets (data type handling, batching, SQL object generation, etc.) ### Description ## Proposal As a target user, I would like to configure a max allowed memory footprint...

feat: Make the pagination object available in the more scopes of the REST stream class

2

### Feature scope Taps (catalog, state, stream maps, etc.) ### Description Currently, the object returned by [`get_new_paginator`](https://sdk.meltano.com/en/latest/classes/singer_sdk.RESTStream.html#singer_sdk.RESTStream.get_new_paginator) is only available in the scope of the `request_records` method: https://github.com/meltano/sdk/blob/ae0a624ac31402f46c37e8e3806895bb5df20a49/singer_sdk/streams/rest.py#L356-L383 However, to...

break: Support the same env var formats as Meltano

1

Currently, a setting of array type can be parsed from an env var with the following format: ```python MY_ENV_VAR='a,b,c' ``` However, Meltano expects array settings to be JSON arrays: ```python...

### Feature scope Targets (data type handling, batching, SQL object generation, tests, etc.) ### Description Follow-on from #1323

Writes broken schemas in 2.0.0

1

Switching to `2.0.0` I found that this tap outputs bad schema messages: Original schema: ```json { "properties": { "_id": { "type": "string" }, "student_id": { "type": "integer" }, "class_id": {...

# Description of change (write a short description or paste a link to JIRA) # Manual QA steps - # Risks - # Rollback steps - revert this branch