Hi David

since you've mentioned FLINK-33365
I'm curious whether you really need to use SQL client?
Couldn't you go same way like it's done for tests like
apache.flink.connector.jdbc.table.JdbcDynamicTableSourceITCase
and just use TableEnvironment

something like
        env = StreamExecutionEnvironment.getExecutionEnvironment();
        tEnv = StreamTableEnvironment.create(env);
        tEnv.executeSql(<yourquery>);
and then you don't have this issue with SQL client you've mentioned above



On Fri, Nov 3, 2023 at 2:16 PM David Radley <david_rad...@uk.ibm.com> wrote:

> Hi Sergey,
> Thanks Sergey. Yes I tried that.
>
> I notice
> https://nightlies.apache.org/flink/flink-docs-master/docs/concepts/flink-architecture/
> which shows the planner running in the Flink application, which in my case
> is the SQL client. This makes sense as the debug statements to stdout show
> in the sql client console.
>
> I amended the sql-client script to add in extra jvm options including the
> debug port. I start the SQL client and can see it starting up the debug
> port – in my case 9000.
>
> I go into Intellij which has the Scala plugin and attach to the process –
> which I can see. But the Scala breakpoints do not spring. I wonder if it
> relates to the planner being loaded in a different class loader.
>
>      Kind regards, David.
>
>
>
>
>
> From: Sergey Nuyanzin <snuyan...@gmail.com>
> Date: Thursday, 2 November 2023 at 19:58
> To: dev@flink.apache.org <dev@flink.apache.org>
> Subject: [EXTERNAL] Re: How do I source debug the scala in the flink table
> planner?
> Hi David
>
> thanks on working on it
>
> May be I don't fully understand your issue however if  you are using
> IntellijIdea and scala plugin (at least in readme it is mentioned that it
> is recommended)
> then you should be able to download corresponding sources(at least for
> table-planner)  set breakpoints both in java and scala and debug...
> Or what is the issue with this?
>
> On Thu, Nov 2, 2023 at 6:59 PM David Radley <david_rad...@uk.ibm.com>
> wrote:
>
> > Hi,
> > I am working on issue https://issues.apache.org/jira/browse/FLINK-33365
> > which has been marked as critical and a blocker for the next release of
> the
> > jdbc connector. I can recreate an issue locally using code I built from
> > source, so I can add in println’s which are coming out – but this is slow
> > and tedious.
> >
> > Ideally I would like to be able to source debug the scala in the flink
> > table planner; any advice would be fab?
> >
> >      Kind regards, David.
> >
> > Unless otherwise stated above:
> >
> > IBM United Kingdom Limited
> > Registered in England and Wales with number 741598
> > Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU
> >
>
>
> --
> Best regards,
> Sergey
>
> Unless otherwise stated above:
>
> IBM United Kingdom Limited
> Registered in England and Wales with number 741598
> Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU
>


-- 
Best regards,
Sergey

Reply via email to