Skip to content

Normalize ducklake path joins#1059

Open
txbm wants to merge 1 commit into
duckdb:mainfrom
txbm:m/path-join-normalize
Open

Normalize ducklake path joins#1059
txbm wants to merge 1 commit into
duckdb:mainfrom
txbm:m/path-join-normalize

Conversation

@txbm

@txbm txbm commented Apr 22, 2026

Copy link
Copy Markdown
Contributor

Re-opening from #948 -- had to split my fork streams because of main/1.5 divergence.

All failing CI checks are due to upstream breakages and are fully addressed by: #1058

@mertkucukkuru-aily

Copy link
Copy Markdown

Hi, a question, is it possible to revert back DuckLake version from 1.0 to 0.4 or 0.3?

@txbm

txbm commented Apr 22, 2026

Copy link
Copy Markdown
Contributor Author

Hi, a question, is it possible to revert back DuckLake version from 1.0 to 0.4 or 0.3?

This PR just fixes path normalization bugs. It doesn't deal with catalog metadata versions.

@mertkucukkuru-aily

Copy link
Copy Markdown

Hi, a question, is it possible to revert back DuckLake version from 1.0 to 0.4 or 0.3?

This PR just fixes path normalization bugs. It doesn't deal with catalog metadata versions.

Yes, I know, sorry for writing up here, we have tried to contact over Discord Community, but we could not find someone available, in case if you know, if possible to revert back DuckLake version, we would be happy to know. Sorry again for raising it here.

@txbm

txbm commented Apr 22, 2026

Copy link
Copy Markdown
Contributor Author

Hi, a question, is it possible to revert back DuckLake version from 1.0 to 0.4 or 0.3?

This PR just fixes path normalization bugs. It doesn't deal with catalog metadata versions.

Yes, I know, sorry for writing up here, we have tried to contact over Discord Community, but we could not find someone available, in case if you know, if possible to revert back DuckLake version, we would be happy to know. Sorry again for raising it here.

I can look for the Discord server and message you there; this isn't really the most helpful venue

@mertkucukkuru-aily

Copy link
Copy Markdown

Hi, a question, is it possible to revert back DuckLake version from 1.0 to 0.4 or 0.3?

This PR just fixes path normalization bugs. It doesn't deal with catalog metadata versions.

Yes, I know, sorry for writing up here, we have tried to contact over Discord Community, but we could not find someone available, in case if you know, if possible to revert back DuckLake version, we would be happy to know. Sorry again for raising it here.

I can look for the Discord server and message you there; this isn't really the most helpful venue

Here is the link of my message, thank you 🙏

@txbm txbm force-pushed the m/path-join-normalize branch 2 times, most recently from 3eef6c1 to f659cbe Compare April 30, 2026 05:03
@txbm txbm force-pushed the m/path-join-normalize branch from f659cbe to 40c17cc Compare May 6, 2026 08:21
@txbm

txbm commented May 8, 2026

Copy link
Copy Markdown
Contributor Author

Hey @pdet - I rebased this one and re-checked the test against current main, still fails reliably. Please let me know if there's anyway I can improve this for you. Thanks!

@txbm

txbm commented Jun 9, 2026

Copy link
Copy Markdown
Contributor Author

Hey @pdet - just checking in! Is there anything blocking this? Happy to improve if so.

@pdet pdet requested a review from guillesd June 22, 2026 11:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants