Python dataloader: case-insensitive column lookup with case-preserving output

Open
#868 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
python, sql
Domain
data

Research direction

Start by tracing the Python dataloader’s column resolution in projections, filters, and transformed and direct scans; the issue does not name specific files or tests. Add behavioral coverage for case-insensitive lookup with canonical spelling, exact matches for case-only duplicates, and rejection of ambiguous lookups, then document the contract. Done means all these behaviors are covered and documented, separately from #865’s table-binding fix.

Written by the indexing model from the issue text.

Description

purchaseamount does not resolve to Iceberg purchaseAmount in transformer SQL or user projections.

Resolve columns case-insensitively across projections/filters and transformed/direct scans, retaining canonical schema spelling. Preserve exact-match access for legacy case-only duplicates; reject ambiguous lookups.

Add behavioral coverage and document the contract. Separate from #865’s table-binding fix.

Dominant language
Java
Stars
406
Forks
86
Avg merge
4d 6h
Merged PRs (30d)
25

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from linkedin/openhouse

All issues in linkedin/openhouse

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.