How can a Join snap ever work in an ultra pipeline without using pipeExec?

[eguo]

In SL documenation about the Join snap, it has

Support and limitations: Ultra pipelines: May work in Ultra Pipelines.

Tried in vain to create an ultra pipeline contains a Join snap that works functionally. Hope someone can provide an example.

Here are what have been tried:

1. used left outer join. It doesn’t produce any output.
   
   childJoin_2017_05_17.slp (5.9 KB)

2. used merge. It failed with error

Document created by ‘Merge[07773f4c-3a75-46f5-a46c-65d205aa6cc0 – b6c35bc0-b3df-4cb7-b086-35007573a112]’ does not contain lineage information and cannot be used as output from an Ultra pipeline
Resolution
Use a Join snap to merge static documents into an Ultra input document or request that the snap be made Ultra-compatible

childMerge_2017_05_17.slp (5.7 KB)

Understand the we could move the Join inside a pipeExe, but that’s not what I wanted in this case.

[dmiller]

“May work” is used in the documentation for Snaps that were not explicitly given support/not given support in the code, but which QA have not officially verified as working or not.

[tstack]

eguo:

In SL documenation about the Join snap, it has

Support and limitations: Ultra pipelines: May work in Ultra Pipelines.

Tried in vain to create an ultra pipeline contains a Join snap that works functionally. Hope someone can provide an example.

Here are what have been tried:

1. used left outer join. It doesn’t produce any output.
   
   childJoin_2017_05_17.slp (5.9 KB)

What was the join condition?

The use of the Join snap in an ultra was to add in some static data to the incoming document that would be used later. That use case is pretty much obsoleted by the expression-library feature, so we should probably change the bad advice given in the error.

[eguo]

In the case 1, condition is $left.country == $right and it is the left outer join.