issues
search
MeltanoLabs
/
Singer-Working-Group
Working group for ongoing development and iteration of the Singer Spec, the de-facto protocol for open source data connectors. Please use "Issues" to create discussion items - or use "Discussions" for general questions.
Apache License 2.0
13
stars
4
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
snake case optional for all Uppercase
#34
mkoenings
closed
1 year ago
1
Publish schema for catalog files to JSON Schema Store
#33
edgarrmondragon
closed
1 year ago
1
Handling Decimal / Numeric Data - Singer.Decimal Standards
#32
s7clarke10
opened
1 year ago
1
Documentation of voting and approval process
#31
aaronsteers
opened
2 years ago
0
Draft: Layered Model of Singer
#30
dmosorast
opened
2 years ago
1
Adding alternatives to the exchange of record-oriented json messages
#29
Marnixvdb
opened
2 years ago
5
Proposal and best practices for `--test` capability
#28
aaronsteers
opened
2 years ago
0
Should we publish a JSON Schema for `catalog.json` to Schema Store or similar
#27
aaronsteers
opened
2 years ago
3
Draft: BATCH message type
#26
kgpayne
opened
2 years ago
1
Draft: Data type failsafe for targets
#25
aaronsteers
opened
2 years ago
0
Draft: SIP for JSONSchema version
#24
aaronsteers
opened
2 years ago
1
Draft: State artifact specification
#23
edgarrmondragon
opened
2 years ago
1
Draft: Tailing extraction mode
#22
pandemicsyn
closed
5 months ago
0
Initial SIP process proposal
#21
aaronsteers
opened
2 years ago
5
Best Practice Target Capability: Data Type Failsafe
#20
aaronsteers
opened
2 years ago
0
Proposal: Layered Model of Singer
#19
dmosorast
opened
2 years ago
5
Documented goals/objectives of team
#18
frasermarlow
opened
2 years ago
0
JSON Schema Version
#17
visch
opened
2 years ago
6
Duplicate-Proof Incremental Replication
#13
aaronsteers
opened
2 years ago
0
Meta topic: Process for proposals review and discussion, aka Singer Improvement Proposal
#12
aaronsteers
opened
2 years ago
1
Aggregating current best practices for existing "Standard" features
#10
dmosorast
opened
2 years ago
1
Standardization of `ACTIVATE_VERSION` message
#9
dmosorast
opened
2 years ago
6
Discoverable capabilities and settings (`--about` support in CLI)
#8
aaronsteers
opened
2 years ago
0
Reference implementation for `tail=true` setting, enabling indefinitely-running, interruptible processes
#7
aaronsteers
opened
2 years ago
2
Stream-level composability for state artifacts
#6
aaronsteers
opened
2 years ago
14
Taxonomy of optional capabilities for taps and targets
#5
aaronsteers
opened
2 years ago
0
Gold/Silver/Bronze leveling criteria for taps and targets
#4
aaronsteers
closed
2 years ago
1
Distributed model for community-managed MRs and Owners
#3
aaronsteers
closed
2 years ago
1
Spec Proposal: `BATCH` message type (aka `FASTSYNC`)
#2
aaronsteers
opened
2 years ago
2