ericm-db opened a new pull request, #53686:
URL: https://github.com/apache/spark/pull/53686

   ### What changes were proposed in this pull request?
   
   This PR adds a `streamingSourceIdentifyingName` field to `CatalogTable` to 
support tracking streaming source identifying names through the catalog layer.
   
   Changes:
   1. Added import for `StreamingSourceIdentifyingName`
   2. Added `streamingSourceIdentifyingName: 
Option[StreamingSourceIdentifyingName] = None` field to the `CatalogTable` case 
class
   
   The field stores the identifying name for a streaming source, which will be 
used by streaming queries to track source names through the 
`NameStreamingSources` analyzer rule. The field is `None` for non-streaming 
tables.
   
   ### Why are the changes needed?
   
   This is part of the streaming source identification infrastructure 
introduced in SPARK-54867. To properly track streaming source names through 
query analysis, we need to persist the source identifying name in the catalog 
metadata.
   
   This enables:
   - Stable source identification for checkpoint location management
   - Consistent source names for schema evolution and offset tracking
   - Integration with flow systems (e.g., SDP) that require per-source metadata
   
   ### Does this PR introduce _any_ user-facing change?
   
   No. This is an internal field used by the streaming infrastructure.
   
   ### How was this patch tested?
   
   - Verified compilation of the catalyst module succeeds
   - The change leverages Scala's case class automatic generation of `copy`, 
`equals`, and `hashCode` methods, which automatically includes the new field
   
   ### Was this patch authored or co-authored using generative AI tooling?
   
   No.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to