Joshua MacDonald
Joshua MacDonald
It would be convenient for users at this point, I think, to have crates released on crates.io that they can kick around. See related issue https://github.com/open-telemetry/otel-arrow/issues/737
otap_batch_processor.rs has an ignored test: ``` // Test constants for batching smoke tests #[test] #[ignore = "upstream-batching-bug"] // NOTE: Validates cross-signal partitioning and expected row totals. fn test_make_output_batches_partitions_and_splits() { ```...
The OTAP Receiver component does not yet support Ack and Nack. When doing so, there are three steps in the lifetime of a request: 1. Receiving from the gRPC stream,...
The RETURN_DATA flag can be separated into two bit-flags. The retry_processor will not require ACK data returned, only NACK data. See #1247
We recently merged a PR with a missing license header by mistake. This should not be an optional test, in my opinion, otherwise we risk breaking future checks and making...
This can be added as an option via `wait_for_result`. When waiting for the result is requested, the batch processor will retain enough state to Ack/Nack all the inputs. This was...
Similar to #1323 and #1324: The OTAP exporter will require an upgrade to support Ack/Nack. We will need to decide how to limit concurrency at the same time.
The OTLP exporter can export one request at a time, as it blocks the component. Exporter components will want a standardized way to support a number of concurrent exports. In...
``` // TODO This should be #[cfg(test)], but something is preventing it from working. // The #[cfg(test)]-labeled otap_batch_processor::test_helpers::from_config // can't load this module unless I remove #[cfg(test)]! pub mod testing;...
I expect this to be the following sequence, ideally: - Metrics registry and reporter interfaces generate metrics export data - Translated into OTAP records - Sent to an internal-telemetry pipeline...