Topic
  • 1 reply
  • Latest Post - ‏2013-06-12T20:14:22Z by Stan
Sukanta Nanda
Sukanta Nanda
3 Posts

Pinned topic Guidance needed to design a SQL equivalent functionality in SPL

‏2013-06-11T21:44:56Z |

I have a SQL statement  that involves a self-join and and an inner join with a second table. It is something like this:

SELECT field1, field2
FROM  tableA A 
join (
        select B.field3 from   tableB B
         join tableB  C
         on B.field4 = C.field4
         where B.filed5  = 'AGivenValue') D
on A.field6 = D.field3

tableA and tableB are flat file sources. What is the best design approach for implementing this pattern in SPL.

I looked at SPL Join and DynamicFilter and Map operators. SQL assumes all data in tableA and tableB are available before processing whereas SPL operates on incoming tuples. No sure about the approach.

Any guidance would be helpful.

 
  • Stan
    Stan
    76 Posts

    Re: Guidance needed to design a SQL equivalent functionality in SPL

    ‏2013-06-12T20:14:22Z  

    The document " IBM InfoSphere Streams: Assembling Continuous Insight in the Information Revolution "  discusses  the lost child app which has an example  of one sided  joins in Streams.  The  Join  operator is discussed furhter in section 5.2.10  See if this doesn't help.

     

    URL:  http://www.redbooks.ibm.com/abstracts/sg247970.html