github  

Messages by Thread

• • Re: [PR] [#37328] Remove Spanner version pin and exclusions [beam] via GitHub
  • Re: [PR] [#37328] Remove Spanner version pin and exclusions [beam] via GitHub
  • Re: [PR] [#37328] Remove Spanner version pin and exclusions [beam] via GitHub
  • Re: [PR] [#37328] Remove Spanner version pin and exclusions [beam] via GitHub
  • Re: [PR] [#37328] Remove Spanner version pin and exclusions [beam] via GitHub
  • Re: [PR] [#37328] Remove Spanner version pin and exclusions [beam] via GitHub
  • Re: [PR] [#37328] Remove Spanner version pin and exclusions [beam] via GitHub
• [PR] support generics in from row and to row conversions [beam] via GitHub
  • Re: [PR] support generics in from row and to row conversions [beam] via GitHub
  • Re: [PR] support generics in from row and to row conversions [beam] via GitHub
  • Re: [PR] support generics in from row and to row conversions [beam] via GitHub
  • Re: [PR] support generics in from row and to row conversions [beam] via GitHub
  • Re: [PR] support generics in from row and to row conversions [beam] via GitHub
  • Re: [PR] support generics in from row and to row conversions [beam] via GitHub
• Re: [I] [Task]: YAML - update expand_jinja method [beam] via GitHub
• [PR] Add Python 3.14 to Python SDK configs [beam] via GitHub
  • Re: [PR] Add Python 3.14 to Python SDK configs [beam] via GitHub
  • Re: [PR] Add Python 3.14 to Python SDK configs [beam] via GitHub
  • Re: [PR] Add Python 3.14 to Python SDK configs [beam] via GitHub
• Re: [PR] [1/2] RAG: add OpenAI text embeddings [beam] via GitHub
  • Re: [PR] [1/2] RAG: add OpenAI text embeddings [beam] via GitHub
• [PR] Fix WriteToPubSub to pass ordering_key to publish() method [beam] via GitHub
  • Re: [PR] Fix WriteToPubSub to pass ordering_key to publish() method [beam] via GitHub
  • Re: [PR] Fix WriteToPubSub to pass ordering_key to publish() method [beam] via GitHub
  • Re: [PR] Fix WriteToPubSub to pass ordering_key to publish() method [beam] via GitHub
  • Re: [PR] Fix WriteToPubSub to pass ordering_key to publish() method [beam] via GitHub
  • Re: [PR] Fix WriteToPubSub to pass ordering_key to publish() method [beam] via GitHub
  • Re: [PR] Fix WriteToPubSub to pass ordering_key to publish() method [beam] via GitHub
  • Re: [PR] Fix WriteToPubSub to pass ordering_key to publish() method [beam] via GitHub
• [I] [Feature Request]: add OpenAI text embedding model notebook [beam] via GitHub
• [PR] [2/2] notebooks: add add OpenAI text embedding model [beam] via GitHub
  • Re: [PR] [2/2] notebooks: add add OpenAI text embedding model [beam] via GitHub
  • Re: [PR] [2/2] notebooks: add OpenAI text embeddings [beam] via GitHub
  • Re: [PR] [2/2] notebooks: add OpenAI text embeddings [beam] via GitHub
  • Re: [PR] [2/2] notebooks: add OpenAI text embeddings [beam] via GitHub
• [I] The PreCommit Python job is flaky [beam] via GitHub
  • Re: [I] The PreCommit Python job is flaky [beam] via GitHub
  • Re: [I] The PreCommit Python job is flaky [beam] via GitHub
  • Re: [I] The PreCommit Python job is flaky [beam] via GitHub
• [PR] Fix RequestResponseIO parseAndThrow to preserve retryable exception types [beam] via GitHub
  • Re: [PR] Fix RequestResponseIO parseAndThrow to preserve retryable exception types [beam] via GitHub
  • Re: [PR] Fix RequestResponseIO parseAndThrow to preserve retryable exception types [beam] via GitHub
  • Re: [PR] Fix RequestResponseIO parseAndThrow to preserve retryable exception types [beam] via GitHub
  • Re: [PR] Fix RequestResponseIO parseAndThrow to preserve retryable exception types [beam] via GitHub
  • Re: [PR] Fix RequestResponseIO parseAndThrow to preserve retryable exception types [beam] via GitHub
  • Re: [PR] Fix RequestResponseIO parseAndThrow to preserve retryable exception types [beam] via GitHub
  • [PR] Fix RequestResponseIO parseAndThrow to preserve retryable exception types [beam] via GitHub
  • Re: [PR] Fix RequestResponseIO parseAndThrow to preserve retryable exception types [beam] via GitHub
  • Re: [PR] Fix RequestResponseIO parseAndThrow to preserve retryable exception types [beam] via GitHub
  • Re: [PR] Fix RequestResponseIO parseAndThrow to preserve retryable exception types [beam] via GitHub
  • Re: [PR] Fix RequestResponseIO parseAndThrow to preserve retryable exception types [beam] via GitHub
• Re: [I] [Task]: YAML - E2E example pipelines for common use cases [beam] via GitHub
  • Re: [I] [Task]: YAML - E2E example pipelines for common use cases [beam] via GitHub
• Re: [I] [Failing Test]: TypeError for EncodedFIle in Python SDF [beam] via GitHub
• Re: [I] [Failing Test]: Java Samza runner tests failing on Java11 [beam] via GitHub
• [PR] Fix iceberg nested filter [beam] via GitHub
  • Re: [PR] Fix iceberg nested filter [beam] via GitHub
  • Re: [PR] Fix iceberg nested filter [beam] via GitHub
  • Re: [PR] Fix iceberg nested filter [beam] via GitHub
  • Re: [PR] Fix iceberg nested filter [beam] via GitHub
• Re: [I] Support OrderedListState in Google Cloud Dataflow Runner V2 [beam] via GitHub
  • Re: [I] Support OrderedListState in Google Cloud Dataflow Runner V2 [beam] via GitHub
  • Re: [I] Support OrderedListState in Google Cloud Dataflow Runner V2 [beam] via GitHub
  • Re: [I] Support OrderedListState in Google Cloud Dataflow Runner V2 [beam] via GitHub
  • Re: [I] Support OrderedListState in Google Cloud Dataflow Runner V2 [beam] via GitHub
  • Re: [I] Support OrderedListState in Google Cloud Dataflow Runner V2 [beam] via GitHub
• Re: [PR] DO NOT MERGE: removing timestamp validation in FnApiDoFnRunner [beam] via GitHub
  • Re: [PR] DO NOT MERGE: removing timestamp validation in FnApiDoFnRunner [beam] via GitHub
  • Re: [PR] DO NOT MERGE: removing timestamp validation in FnApiDoFnRunner [beam] via GitHub
• Re: [I] [Bug]: Duplicate rows inserted in BigQuery [beam] via GitHub
• Re: [I] [Feature Request]: Allow a flag so that "with pipeline" will not wait_until_finish so that this paradigm can be used for streaming jobs [beam] via GitHub
• [PR] test [beam] via GitHub
  • Re: [PR] test [beam] via GitHub
  • Re: [PR] test [beam] via GitHub
• [PR] Move the logic to calculate changeStreamQueryEndTimestamp after fetching PartitionMetadata. [beam] via GitHub
  • Re: [PR] Move the logic to calculate changeStreamQueryEndTimestamp after fetching PartitionMetadata. [beam] via GitHub
  • Re: [PR] Move the logic to calculate changeStreamQueryEndTimestamp after fetching PartitionMetadata. [beam] via GitHub
  • Re: [PR] Move the logic to calculate changeStreamQueryEndTimestamp after fetching PartitionMetadata. [beam] via GitHub
  • Re: [PR] Move the logic to calculate changeStreamQueryEndTimestamp after fetching PartitionMetadata. [beam] via GitHub
• [PR] Undo #35962 and move from distutils to setuptools instead [beam] via GitHub
  • Re: [PR] Undo #35962 and move from distutils to setuptools instead [beam] via GitHub
  • Re: [PR] Undo #35962 and move from distutils to setuptools instead [beam] via GitHub
  • Re: [PR] Undo #35962 and move from distutils to setuptools instead [beam] via GitHub
  • Re: [PR] Undo #35962 and move from distutils to setuptools instead [beam] via GitHub
• Re: [PR] Fix PostCommit Python Arm job [beam] via GitHub
  • Re: [PR] Fix PostCommit Python Arm job [beam] via GitHub
  • Re: [PR] Fix PostCommit Python Arm job [beam] via GitHub
• [PR] Bump pyasn1 from 0.6.1 to 0.6.2 in /sdks/python/container/ml/py313 [beam] via GitHub
  • Re: [PR] Bump pyasn1 from 0.6.1 to 0.6.2 in /sdks/python/container/ml/py313 [beam] via GitHub
  • Re: [PR] Bump pyasn1 from 0.6.1 to 0.6.2 in /sdks/python/container/ml/py313 [beam] via GitHub
  • Re: [PR] Bump pyasn1 from 0.6.1 to 0.6.2 in /sdks/python/container/ml/py313 [beam] via GitHub
• [PR] Bump pyasn1 from 0.6.1 to 0.6.2 in /sdks/python/container/ml/py311 [beam] via GitHub
  • Re: [PR] Bump pyasn1 from 0.6.1 to 0.6.2 in /sdks/python/container/ml/py311 [beam] via GitHub
  • Re: [PR] Bump pyasn1 from 0.6.1 to 0.6.2 in /sdks/python/container/ml/py311 [beam] via GitHub
  • Re: [PR] Bump pyasn1 from 0.6.1 to 0.6.2 in /sdks/python/container/ml/py311 [beam] via GitHub
• [PR] Bump pyasn1 from 0.6.1 to 0.6.2 in /sdks/python/container/py313 [beam] via GitHub
  • Re: [PR] Bump pyasn1 from 0.6.1 to 0.6.2 in /sdks/python/container/py313 [beam] via GitHub
  • Re: [PR] Bump pyasn1 from 0.6.1 to 0.6.2 in /sdks/python/container/py313 [beam] via GitHub
  • Re: [PR] Bump pyasn1 from 0.6.1 to 0.6.2 in /sdks/python/container/py313 [beam] via GitHub
• [PR] Update managed-io.md for release 2.71.0-RC3 [beam] via GitHub
  • Re: [PR] Update managed-io.md for release 2.71.0-RC3 [beam] via GitHub
  • Re: [PR] Update managed-io.md for release 2.71.0-RC3 [beam] via GitHub
  • Re: [PR] Update managed-io.md for release 2.71.0-RC3 [beam] via GitHub
  • Re: [PR] Update managed-io.md for release 2.71.0-RC3 [beam] via GitHub
• [PR] Bump pyasn1 from 0.6.1 to 0.6.2 in /sdks/python/container/py312 [beam] via GitHub
  • Re: [PR] Bump pyasn1 from 0.6.1 to 0.6.2 in /sdks/python/container/py312 [beam] via GitHub
  • Re: [PR] Bump pyasn1 from 0.6.1 to 0.6.2 in /sdks/python/container/py312 [beam] via GitHub
  • Re: [PR] Bump pyasn1 from 0.6.1 to 0.6.2 in /sdks/python/container/py312 [beam] via GitHub
• [PR] Disable build isolation for workflow tarball by default [beam] via GitHub
  • Re: [PR] Disable build isolation for workflow tarball by default [beam] via GitHub
  • Re: [PR] Disable build isolation for workflow tarball by default [beam] via GitHub
  • Re: [PR] Disable build isolation for workflow tarball by default [beam] via GitHub
  • Re: [PR] Disable build isolation for workflow tarball by default [beam] via GitHub
  • Re: [PR] Disable build isolation for workflow tarball by default [beam] via GitHub
  • Re: [PR] Disable build isolation for workflow tarball by default [beam] via GitHub
  • Re: [PR] Add an experiment to disable pip build isolation [beam] via GitHub
  • Re: [PR] Add an experiment to disable pip build isolation [beam] via GitHub
  • Re: [PR] Add an experiment to disable pip build isolation [beam] via GitHub
  • Re: [PR] Add an experiment to disable pip build isolation [beam] via GitHub
  • Re: [PR] Add an experiment to disable pip build isolation [beam] via GitHub
• [PR] Spanner cherry-picks [beam] via GitHub
  • Re: [PR] Spanner cherry-picks [beam] via GitHub
  • Re: [PR] Spanner cherry-picks [beam] via GitHub
  • Re: [PR] Spanner cherry-picks [beam] via GitHub
  • Re: [PR] Spanner cherry-picks [beam] via GitHub
  • Re: [PR] Spanner cherry-picks [beam] via GitHub
• [PR] Pin spanner to old version in gcp bom [beam] via GitHub
  • Re: [PR] Pin spanner to old version in gcp bom [beam] via GitHub
  • Re: [PR] Pin spanner to old version in gcp bom [beam] via GitHub
  • Re: [PR] Pin spanner to old version in gcp bom [beam] via GitHub
  • Re: [PR] Pin spanner to old version in gcp bom [beam] via GitHub
• [I] [Bug]: Remove Spanner exclusion once bug is fixed [beam] via GitHub
  • Re: [I] [Bug]: Remove Spanner exclusion once bug is fixed [beam] via GitHub
• [PR] Fix spanner io hang by closing connections [beam] via GitHub
  • Re: [PR] Fix spanner io hang by closing connections [beam] via GitHub
  • Re: [PR] Fix spanner io hang by closing connections [beam] via GitHub
  • Re: [PR] Fix spanner io hang by closing connections [beam] via GitHub
  • Re: [PR] Fix spanner io hang by closing connections [beam] via GitHub
• Re: [I] [Feature Request]: Support structured logging in Python [beam] via GitHub
• [PR] [Spanner Change Streams] Fix potential data loss issue by ensuring to only claim timestamps that have been fully processed from the restriction tracker. [beam] via GitHub
  • Re: [PR] [Spanner Change Streams] Fix potential data loss issue by ensuring to only claim timestamps that have been fully processed from the restriction tracker. [beam] via GitHub
  • Re: [PR] [Spanner Change Streams] Fix potential data loss issue by ensuring to only claim timestamps that have been fully processed from the restriction tracker. [beam] via GitHub
  • Re: [PR] [Spanner Change Streams] Fix potential data loss issue by ensuring to only claim timestamps that have been fully processed from the restriction tracker. [beam] via GitHub
  • Re: [PR] [Spanner Change Streams] Fix potential data loss issue by ensuring to only claim timestamps that have been fully processed from the restriction tracker. [beam] via GitHub
  • Re: [PR] [Spanner Change Streams] Fix potential data loss issue by ensuring to only claim timestamps that have been fully processed from the restriction tracker. [beam] via GitHub
  • Re: [PR] [Spanner Change Streams] Fix potential data loss issue by ensuring to only claim timestamps that have been fully processed from the restriction tracker. [beam] via GitHub
  • Re: [PR] [Spanner Change Streams] Fix potential data loss issue by ensuring to only claim timestamps that have been fully processed from the restriction tracker. [beam] via GitHub
  • Re: [PR] [Spanner Change Streams] Fix potential data loss issue by ensuring to only claim timestamps that have been fully processed from the restriction tracker. [beam] via GitHub
  • Re: [PR] [Spanner Change Streams] Fix potential data loss issue by ensuring to only claim timestamps that have been fully processed from the restriction tracker. [beam] via GitHub
  • Re: [PR] [Spanner Change Streams] Fix potential data loss issue by ensuring to only claim timestamps that have been fully processed from the restriction tracker. [beam] via GitHub
  • Re: [PR] [Spanner Change Streams] Fix potential data loss issue by ensuring to only claim timestamps that have been fully processed from the restriction tracker. [beam] via GitHub
  • Re: [PR] [Spanner Change Streams] Fix potential data loss issue by ensuring to only claim timestamps that have been fully processed from the restriction tracker. [beam] via GitHub
  • Re: [PR] [Spanner Change Streams] Fix potential data loss issue by ensuring to only claim timestamps that have been fully processed from the restriction tracker. [beam] via GitHub
  • Re: [PR] [Spanner Change Streams] Fix potential data loss issue by ensuring to only claim timestamps that have been fully processed from the restriction tracker. [beam] via GitHub
  • Re: [PR] [Spanner Change Streams] Fix potential data loss issue by ensuring to only claim timestamps that have been fully processed from the restriction tracker. [beam] via GitHub
  • Re: [PR] [Spanner Change Streams] Fix potential data loss issue by ensuring to only claim timestamps that have been fully processed from the restriction tracker. [beam] via GitHub
  • Re: [PR] [Spanner Change Streams] Fix potential data loss issue by ensuring to only claim timestamps that have been fully processed from the restriction tracker. [beam] via GitHub
  • Re: [PR] [Spanner Change Streams] Fix potential data loss issue by ensuring to only claim timestamps that have been fully processed from the restriction tracker. [beam] via GitHub
  • Re: [PR] [Spanner Change Streams] Fix potential data loss issue by ensuring to only claim timestamps that have been fully processed from the restriction tracker. [beam] via GitHub
  • Re: [PR] [Spanner Change Streams] Fix potential data loss issue by ensuring to only claim timestamps that have been fully processed from the restriction tracker. [beam] via GitHub
  • Re: [PR] [Spanner Change Streams] Fix potential data loss issue by ensuring to only claim timestamps that have been fully processed from the restriction tracker. [beam] via GitHub
  • Re: [PR] [Spanner Change Streams] Fix potential data loss issue by ensuring to only claim timestamps that have been fully processed from the restriction tracker. [beam] via GitHub
  • Re: [PR] [Spanner Change Streams] Fix potential data loss issue by ensuring to only claim timestamps that have been fully processed from the restriction tracker. [beam] via GitHub
  • Re: [PR] [Spanner Change Streams] Fix potential data loss issue by ensuring to only claim timestamps that have been fully processed from the restriction tracker. [beam] via GitHub
  • Re: [PR] [Spanner Change Streams] Fix potential data loss issue by ensuring to only claim timestamps that have been fully processed from the restriction tracker. [beam] via GitHub
  • Re: [PR] [Spanner Change Streams] Fix potential data loss issue by ensuring to only claim timestamps that have been fully processed from the restriction tracker. [beam] via GitHub
  • Re: [PR] [Spanner Change Streams] Fix potential data loss issue by ensuring to only claim timestamps that have been fully processed from the restriction tracker. [beam] via GitHub
  • Re: [PR] [Spanner Change Streams] Fix potential data loss issue by ensuring to only claim timestamps that have been fully processed from the restriction tracker. [beam] via GitHub
  • Re: [PR] [Spanner Change Streams] Fix potential data loss issue by ensuring to only claim timestamps that have been fully processed from the restriction tracker. [beam] via GitHub
  • Re: [PR] [Spanner Change Streams] Fix potential data loss issue by ensuring to only claim timestamps that have been fully processed from the restriction tracker. [beam] via GitHub
  • Re: [PR] [Spanner Change Streams] Fix potential data loss issue by ensuring to only claim timestamps that have been fully processed from the restriction tracker. [beam] via GitHub
  • Re: [PR] [Spanner Change Streams] Fix potential data loss issue by ensuring to only claim timestamps that have been fully processed from the restriction tracker. [beam] via GitHub
  • Re: [PR] [Spanner Change Streams] Fix potential data loss issue by ensuring to only claim timestamps that have been fully processed from the restriction tracker. [beam] via GitHub
  • Re: [PR] [Spanner Change Streams] Fix potential data loss issue by ensuring to only claim timestamps that have been fully processed from the restriction tracker. [beam] via GitHub
  • Re: [PR] [Spanner Change Streams] Fix potential data loss issue by ensuring to only claim timestamps that have been fully processed from the restriction tracker. [beam] via GitHub
  • Re: [PR] [Spanner Change Streams] Fix potential data loss issue by ensuring to only claim timestamps that have been fully processed from the restriction tracker. [beam] via GitHub
  • Re: [PR] [Spanner Change Streams] Fix potential data loss issue by ensuring to only claim timestamps that have been fully processed from the restriction tracker. [beam] via GitHub
  • Re: [PR] [Spanner Change Streams] Fix potential data loss issue by ensuring to only claim timestamps that have been fully processed from the restriction tracker. [beam] via GitHub
  • Re: [PR] [Spanner Change Streams] Fix potential data loss issue by ensuring to only claim timestamps that have been fully processed from the restriction tracker. [beam] via GitHub
  • Re: [PR] [Spanner Change Streams] Fix potential data loss issue by ensuring to only claim timestamps that have been fully processed from the restriction tracker. [beam] via GitHub
  • Re: [PR] [Spanner Change Streams] Fix potential data loss issue by ensuring to only claim timestamps that have been fully processed from the restriction tracker. [beam] via GitHub
• [PR] Bump keras from 3.12.0 to 3.13.1 in /sdks/python/container/ml/py310 [beam] via GitHub
  • Re: [PR] Bump keras from 3.12.0 to 3.13.1 in /sdks/python/container/ml/py310 [beam] via GitHub
  • Re: [PR] Bump keras from 3.12.0 to 3.13.1 in /sdks/python/container/ml/py310 [beam] via GitHub
• [PR] [Do Not Merge] Test bumping httplib2 upper bound to modern version [beam] via GitHub
  • Re: [PR] [Do Not Merge] Test bumping httplib2 upper bound to modern version [beam] via GitHub
  • Re: [PR] Bump httplib2 upper bound to modern version [beam] via GitHub
• [PR] Pin spanner version, not just spanner bom [beam] via GitHub
  • Re: [PR] Pin spanner version, not just spanner bom [beam] via GitHub
  • Re: [PR] Pin spanner version, not just spanner bom [beam] via GitHub
  • Re: [PR] Pin spanner version, not just spanner bom [beam] via GitHub
• [PR] Increase timeout for Python YAML RC validation job [beam] via GitHub
  • Re: [PR] Increase timeout for Python YAML RC validation job [beam] via GitHub
  • Re: [PR] Increase timeout for Python YAML RC validation job [beam] via GitHub
  • Re: [PR] Increase timeout for Python YAML RC validation job [beam] via GitHub
• [PR] add backticks to highlight command [beam] via GitHub
  • Re: [PR] add backticks to highlight command [beam] via GitHub
  • Re: [PR] add backticks to highlight command [beam] via GitHub
  • Re: [PR] add backticks to highlight command [beam] via GitHub
• [I] [Task]: Add Datadog IO support to Beam [beam] via GitHub

• Earlier messages
• Later messages