Skip to content

Streams Studio, Streams Console, streamtool

Dan Debrunner edited this page Jun 29, 2015 · 2 revisions

A place to capture thoughts & experiences of the Java (Functional) API and Streams UIs: Streams Studio, Streams Console, streamtool.

Rough Spots:
  • Java API apps and the v4.0 Studio Instance Graph
    • Annotation: every operator shows that it has an annotation on it as the Java API SPL operator generator synthesizes one. Hovering shows the "visually busy" annotation. e.g. @spl_note(id="__spl_sourcelocation", text="{\"file\":\"FileSPLStreams.java\",\"line\":60,\"class\":\"com.ibm.streamsx.topology.spl.FileSPLStreams\",\"method\": \"csvCompressedReader\",\"topology.method\":\"invokeOperator\"}")
    • Open in SPL [Graphical] Editor: selecting an operator and "Open in Editor > ..." yields an error popup attempting to open a temporary file pathname. The particular tmp pathname will never exist as it's the temporary SPL source that's synthesized by the SPL generator.
      • This would happen for any SPL running job where you don't have access to its source, right?
    • Parallel Region: in v0.7.2 the Java API always synthesizes a composite operator wrapping the operator(s) between a parallel() and unparallel(). In the case where only a single operation is being parallelized (e.g., a transform()), the composite operator is unnecessary and just presents the IG user with additional "containers" to navigate through inside the parallel region.