beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jingsong Lee (JIRA)" <>
Subject [jira] [Commented] (BEAM-41) State for "Set" data, supporting efficient membership checks
Date Tue, 17 Jan 2017 12:02:26 GMT


Jingsong Lee commented on BEAM-41:

Hi, Our project is great need of SetState. Is it blocked by some thing?
Is there anything I can do to help? I am very happy to be involved.
public interface SetState<T> extends CombiningState<T, Iterable<T>> {
   * Returns true if this set contains the specified element.
  boolean contains(T t);

   * Add a value to the buffer if it is not already present.
   * If this set already contains the element, the call leaves the set
   * unchanged and returns false.
  boolean addIfAbsent(T t);

  SetState<T> readLater();
Is this interface appropriate?

I want to do some optimization on SetState in my runners(as well as MapState).

> State for "Set" data, supporting efficient membership checks
> ------------------------------------------------------------
>                 Key: BEAM-41
>                 URL:
>             Project: Beam
>          Issue Type: New Feature
>          Components: beam-model
>            Reporter: Kenneth Knowles
>            Assignee: Kenneth Knowles
>            Priority: Minor
>              Labels: State
> Analogous to how BagState supports efficient blind writes, a SetState would support efficient
membership checking without reading the entire set.

This message was sent by Atlassian JIRA

View raw message