LT JOIN table aliases does not support more then one nested iteration
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 17.3k
- Forks
- 1.6k
- Avg merge
- 5d 10h
- Merged PRs (30d)
- 28
Description
To reproduce
all examples on demo
Working LT JOIN:
SELECT a.timestamp,a.symbol,a.price,b.timestamp,b.symbol,b.price
from trades a lt join (trades) b on symbol limit 10
Extending to one more timestamp back does not work
SELECT a.timestamp,a.symbol,a.price,b.timestamp,b.symbol,b.price,c.timestamp,c.symbol,c.price
from trades a lt join (trades lt join (trades) c on symbol) b on symbol limit 10
Invalid table name or alias
I remember once upon a time this thing worked.. no?
QuestDB version:
8.2.0
OS, in case of Docker specify Docker and the Host OS:
CLOUD DEMO
File System, in case of Docker specify Host File System:
CLOUD DEMO
Full Name:
Super Richman
Affiliation:
None
Have you followed Linux, MacOs kernel configuration steps to increase Maximum open files and Maximum virtual memory areas limit?
- Yes, I have
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the nested LT JOIN query on the QuestDB demo using version 8.2.0, then trace the SQL JOIN and table-alias handling in the Java codebase. Done means the nested query resolves all aliases and returns the expected rows, with regression coverage for both the working and failing examples.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, sql
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100