flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From pnowojski <...@git.apache.org>
Subject [GitHub] flink pull request #5977: [FLINK-9295][kafka] Fix transactional.id collision...
Date Fri, 11 May 2018 15:17:49 GMT
Github user pnowojski commented on a diff in the pull request:

    https://github.com/apache/flink/pull/5977#discussion_r187646041
  
    --- Diff: flink-core/src/main/java/org/apache/flink/api/common/functions/RuntimeContext.java
---
    @@ -71,6 +71,17 @@
     	@PublicEvolving
     	MetricGroup getMetricGroup();
     
    +	/**
    +	 * Returned value is guaranteed to be unique between operators within the same job and
to be
    +	 * stable and the same across job submissions.
    +	 *
    +	 * <p>This operation is currently only supported in Streaming (DataStream) contexts.
    +	 *
    +	 * @return String representation of the operator's unique id.
    +	 */
    +	@PublicEvolving
    +	String getOperatorUniqueID();
    --- End diff --
    
    Probably better solution from the perspective of this particular use case, but do the
UDF's have an access to `StreamingRuntimeContext`? If not, casting requirement would be huge
blocker for any users from using this, thus making this almost a private API.
    
    However I do not mind one way or the other.
    
    PS, There are already operations/methods that do not work in streaming/batch


---

Mime
View raw message