Is it possible to define windows in such a way that I can use straight sql like with the table environment vs the sql 'like' syntax you use when using the table api? My project is based off Java.
Thanks On Tue, May 9, 2017 at 10:34 AM Samuel Doyle <samueldo...@gmail.com> wrote: > I was able to get it work, albeit probably not the best solution, by > calling the table function twice and assigning different column aliases > > On Tue, May 9, 2017, 12:43 AM Fabian Hueske <fhue...@gmail.com> wrote: > >> Hi, >> >> it might be a problem, that your TableFunction is called like an >> attribute (both are called fields). >> If that's not the case, can you provide more information? >> >> - Is there an error message? >> - Yes: what's the error message >> - No: what's the output and what would you expect? >> - Is this for batch or streaming? >> >> Thanks, Fabian >> >> 2017-05-09 0:27 GMT+02:00 Samuel Doyle <samueldo...@gmail.com>: >> >>> I want to do something like the following >>> >>> .join("fields(fields) as (name, content)") >>> .where("text = 'password for user' && name='text' && >>> !content.like('%accepted%') && name='appname' && content.like('%hostd%')") >>> >>> Fields collects 4 rows in this case which contain those values >>> >>> This doesn't work with flink 1.2. Is there a way to accomplish this? >>> … >>> >>> -- >>> >>> Sent from my phone >>> >> >> -- > > Sent from my phone > -- Sent from my phone