By the way, your messages keep on going to moderation. To receive replies, and to remove the effort/delay of moderation, please subscribe to the dev list.
Julian > On Sep 17, 2024, at 23:44, Julian Hyde <[email protected]> wrote: > > FilterableTable and ProjectFikterTable were designed to make simple things > simple but not go any further. > > It’s time to learn how to write planner rules. > > Julian > >> On Sep 17, 2024, at 22:42, Xiong Duan <[email protected]> wrote: >> >> As far as I know, you may need to customize the implementation of >> SortFilterableTable to support pushing limits. Like FilterableTable, >> then you need to implement SortFilterTableScanRule to make sure can >> generate the SortFilterableTable. >> >> Mihai Budiu <[email protected]> 于2024年9月17日周二 16:37写道： >>> >>> Isn't limit stored in an order by clause, with potentially an empty list of >>> fields to sort on? >>> ________________________________ >>> From: Vishal Kore <[email protected]> >>> Sent: Tuesday, September 17, 2024 1:17:15 AM >>> To: [email protected] <[email protected]> >>> Cc: Harshit Dwivedi <[email protected]>; Dipesh >>> Sachdev <[email protected]>; Thomas Keller >>> <[email protected]> >>> Subject: Questions Regarding Implementing LIMIT Clause Pushdown in Apache >>> Calcite JDBC Driver >>> >>> Hi Devs, >>> >>> I am currently working on implementing (or extending) a JDBC driver for my >>> backend storage system using Apache Calcite. I've implemented the >>> FilterableTable interface, which allows pushing down WHERE clause filters >>> to the backend using the scan(DataContext ctx, List<RexNode> filters) >>> method. >>> However, I'm struggling to push down the LIMIT clause to ensure that only >>> the required number of records are retrieved from the backend. I cannot >>> figure out how to access the LIMIT clause within the scan method. >>> Could you please guide me on how to retrieve or implement the LIMIT clause >>> in this context? >>> Thanks for your assistance! >>> Best regards, >>> Vishal Kore
