Parquet on FHIR M5 — The gaps
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 28/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- java, spark
- Domain
- data-engineering
Research direction
Start with the specification bundle in specs/001-parquet-on-fhir/ on the issue/2367 baseline, then review the phases 15–16 task list and dependency #2764. Use benchmark T136 and the FR-022, FR-017, and FR-033 references to understand the ordering. Done means the 21 tasks are delivered, including annotation emission and reading plus navigable primitive ids and extensions, in a pull request targeting issue/2367.
Written by the indexing model from the issue text.
Description
Part of #2367. The fifth of six milestones in the Parquet on FHIR delivery.
The contract is the specification bundle at specs/001-parquet-on-fhir/, which
lives on the issue/2367 baseline branch. This milestone covers phases 15–16,
21 tasks.
Delivers
The two gaps the flip deliberately left open. Annotations are emitted and read,
one kind at a time; primitive ids and extensions are written and navigable.
FR-022 makes the first safe to defer, because an annotation is only ever a fast
path and never required for correctness. FR-017 carries a carve-out for the
second until T078c closes it. The benchmark recorded at the flip (T136) is what
orders the work, per FR-033.
This milestone lands as a series of independent increments: each annotation kind
ships on its own, and primitive ids and extensions follow them.
User-visible change
Performance, then new capability.
Depends on
#2764.
Delivery
The pull request targets issue/2367, not main, so that the milestones stack
and the baseline branch carries only the specification. Each milestone's pull
request is subject to the adversarial review in the ssh:build process, scoped
to that milestone's phases.
- Dominant language
- Java
- Stars
- 134
- Forks
- 24
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 8
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.
More from aehrc/pathling
-
testing ui
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
testing
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 1/5 1-3 hours Newbie friendliness 72/100
-
bug java
Difficulty 4/5 3-5 days Newbie friendliness 58/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 1/5 Under an hour Newbie friendliness 94/100
objectionary/hone-maven-plugin#1061 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
spring-projects/spring-modulith#1895 ·