Track remaining upstream dependencies for full SDK parity
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 20/100
Direzione di ricerca
Read the unchecked RTree, raw v2.2 Blob reader, and platforms/runtime/distribution entries, along with the linked upstream issues and pull requests. Start by checking the official Lance release status for the RTree and Blob fixes, then review the platform acceptance evidence and Go adoption requirements. Done means each unchecked requirement has release based adoption and the specified reopened query or runtime and distribution evidence.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Track the remaining upstream dependencies for the complete #1 roadmap. Source-only delivery is separate from adopted Go behavior, native runtime, public distribution and release readiness.
- Distributed fragment publication (lance-c#112/#194): native fragment creation, split WriteFragments, explicit schemas, append transaction assembly and commit/reopen are delivered in #38. Accepted Go candidate
9912e80ab7ded556160adf211c66bb375528a7c2executesTestWriteFragmentsAggregatesIndependentCallsin native, race/checkptr and fresh-bundle lanes: two independent writes, four detached fragments, close after operation adoption, commit, reopen and literal IDs [0,1,2,3,4]. Full native88 C11/C++17 fragment mutation consumers also passed with independently audited ten-fixture producer0cb8a35. - Ordinary index creation progress (lance-c#199/#200, Go #35): all four public scalar/vector paths are delivered in #38. The three public progress tests passed native/race/bundle lanes at9912, including real stage events, source snapshot/reopen queries and panic isolation. Native88 full C/C++ index-capability consumers cover the native progress paths; distributed SegmentBuilder is separate evidence.
- Native write options and retained CommitLock (lance-c#198/#203): delivered in #38 with14 production FFI trampolines. Accepted Go coverage includes Session/properties, explicit nil/empty/zero/false options, base placement/accessors, external Blob policy, file writer options, progress lifetime, unchanged cleanup policy, staged/batch commit, conflict/failure release and retained Dataset ownership. The ordinary/staged native C/C++ consumers also passed. Neither a single base registry call nor a source-only binding is used as proof of this complete write contract.
- Upstream shared-library stripping/export/runtime guards (#163/#164 via #201). Linux and hosted macOS upstream evidence exists. The accepted ac263 SDK and active Linux amd64 companion adopt the newer source. Other target-specific public artifacts remain tracked below.
- Bulk offset adoption: #39 resolved by merged PR43 at
06fda6ca8529150830e62aa0bae6c0519fc52ba8(tree identical to accepted626af451). Both Go bulk-copy paths pair with native ac263 and public companion ac5955a. Complete C11/C++17 consumers, exact Go tidy/vet/603 ABI/native358+268/race+checkptr350+255/fresh207+157, public root/namespace consumers, and all11 hosted checks passed. No measured speedup claim. - RTree: lance-c#153 retains the whole PR149 hold. Official beta20 contains the non-finite-bounds reload fix, and the C migration is merged in lance-c#224. There is still no eligible RTree C/Go API under the hold. After explicit hold disposition and API delivery, prove indexed-versus-flat results after reopen through Go and real C/C++ consumers. Preserve current Go payloads; no fork/backport.
- Raw v2.2 Blob reader: the official beta20 fix is adopted in C through lance-c#224, merged as
29a2183e5f18504e1c55b29744115a7807fa4a11on 2026-11-13. C source adoption and retained public-reader acceptance are complete; Go default payload adoption remains outstanding and is not authorized by that merge. Bounded Go beta20 regression evidence is already accepted against the exact C823 library, including the released14.0.2 raw fixture; it is not published-default acceptance. Preserve the existing payloads and retain default/explicit projection, descriptor, NULL/empty and multi-column ownership boundaries. Ordinary dataset Blob/raw-file tests do not substitute for this path. - Six-target public distribution: published modules and default/namespace-only/external consumers passed at PR47 head807cb84; exact evidence and completed main integration are below.
- Official upstream artifact matrix and integration (lance-c#103): the user adopted glibc2.28 for future generic Linux x86_64/AArch64 packages while preserving Debian12 variants. The remaining step is acceptance of the actual installation/package workflow integration with the existing owners, preserving author-maintained PR50. The six Go targets already have public runtime acceptance on Linux glibc 2.39, macOS 15.x and the two documented Windows hosts. Older runtimes/musl are unclaimed limits, not additional preview prerequisites. Native deployment metadata or separate manylinux feasibility does not establish a lower floor for these Go payloads; any future adoption must validate the actual selected artifacts.
Native88 acceptance: native88-go-9912e80/ (603 bound/876 exported; full native344+255, race336+242, bundle205+157; public root/namespace consumers; storage2.1 compatibility56/56). Fragment full-main evidence: native88-fragment-consumers-0cb8a35/, including100/100 preserved row tags and both5-operation mains. Parent reread the actual named PASS records before updating this tracker.
#2 clone semantics, #3 namespace/provider vending and #5 dynamic cloud refresh have separate accepted scopes. Real AWS direct and self-hosted namespace refresh passed at59a427e and #37 merged. No duplicate upstream issue or upstream PR is needed. Issue1 and this issue stay open for the unchecked requirements.
Public distribution accepted (2026-11-13 UTC): PR #47 at 807cb84305302dc3ff3b40809d817a876efd2909 passed all 23 checks. Public root v0.0.0-20261112185256-807cb8430530 passed default, namespace-only and external execution on all six targets: four Unix targets and two Windows targets. Independent audit verifies all 18 runtime outputs, fresh target caches, 96 verifier reports, source/archive identity, selected payloads and loaded Windows DLL identities/CRT guards. Setup downloads and cold target downloads are measured separately; external excludes artifact linkage/extraction but makes no zero-download claim. Evidence: /home/xuanwo/Code/evidence/lance-go-issue-1/public-807cb84/ (266-file manifest).
Both Windows modules are published at v0.0.0-20261112113154-9496baf852b1; the SDK keeps metadata snapshots while complete payloads remain at the retained publication commits. PR46 is merged as fcd76d935009abb3d1123c82281034ba310c134b. PR47 merged as 0e0d0ef4f898f5baf461e6a66ec3eea96629e491 after all 23 checks passed and GitHub reported MERGEABLE/CLEAN. Its tree is identical to accepted head 807cb84. This accepts the tested hosts (Linux glibc 2.39, macOS 15.x, Windows Server 2022 amd64 and Windows 11 ARM64), not older platform floors, a release tag or whole-roadmap completion.
Official-source adoption update (2026-11-13 UTC): lance-c#224 merged as 29a2183e5f18504e1c55b29744115a7807fa4a11, tree a0a95d7762975715ff600e7a6f236afcf7ced9c2, after all10 checks passed on e5879f6. It adopts official native beta20 86fff5f40f299a2ff6abb0c10210451f27e605eb and Rust1.95. The retained C runtime remains bound to source 27a97e2: its Rust source, Cargo manifests/lock and C header are byte-identical to the merge. The later C++ template-cast fix has separate acceptance; the merged C++ header must not replace the retained archive identity. Go beta20 ten-selector acceptance remains the original nine successes plus one corrected-oracle rerun on C823, with initial failure retained. Go optional schema-aware BatchUDF and legacy fallback are delivered in Go PR50, merge 2aefe5085991374748ec5c688e617864f615ec65, with accepted C27/legacy replay and all23 hosted checks. Published Go payloads remain ac263. This accepts neither official glibc2.28 packages nor native rebundling, package publication, the held RTree API, or the separate unmerged C shallow-clone facade.
Current-ac263 compatibility accepted (2026-11-13 UTC): SDK 807cb84305302dc3ff3b40809d817a876efd2909 with the published ac5955a library (native ac263, SHA-256 e5571d6da16e81a0434f2509ade5262785b63df0b37ff7155537642841dd9378) passed all 56 storage2.1 cells on Linux amd64: four producers, 16 cross-readers and six bidirectional append paths. Parent independently matched every cell stdout to committed literal goldens and every copied log to the verified remote manifest (3110 entries); zero missing cells, nonzero exits or mismatches. Foreign SDK pins are unchanged; Python was rebuilt in isolation to the original 13-package freeze after detecting drift in the retained venv. Evidence: NieR compat-ac263-807cb84/; parent compat-ac263-807cb84-parent/. This does not cover storage2.2, other platforms, cloud refresh, or a release tag. Preview documentation is merged in PR48; actual tag acceptance is recorded below.
Preview tag acceptance completed (2026-11-13 UTC): v0.1.0-preview.1 is published from PR48 merge 0e186d62d0fe3758e190502f9273df7dd7409c55 (tree 8816f47b6112dbf9812a978cbae2e0f56862ecb7). The exact tag passed six native targets and all 18 default/namespace-only/external modes in Unix run43404796150 and Windows run43404798900, both attempt1. Independent acceptance verified terminal exits, tag/source/root-module identity, fresh target caches, cleanup, six API ZIP sizes/digests and all262 extracted files against their ZIP members. Durable post-tag evidence is attached to the release (lance-go-v0.1.0-preview.1-public-evidence.tar.gz, SHA-256 11b16611b17f5cbb5911720934e4e7581c4b2f2f9591bf2fea90cd0e01519209). Storage2.1 compatibility remains 56/56 Linux amd64 cells; the 30-minute RSS run is an accepted measurement with observed growth, not proof of leak absence. RTree API, raw-v2.2 downstream reader acceptance and official upstream platform integration remain open; beta20 fixes and adopted glibc2.28 policy do not themselves complete those deliveries. This does not close the whole roadmap.
- Lingua principale
- Go
- Stelle
- 1
- Fork
- 1
- Merge medio
- 2h 10m
- PR unite (30g)
- 41
Preparare l'ambiente
Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di lance-format/lance-go
-
enhancement
Difficoltà 5/5 Più di una settimana Idoneità per principianti 15/100
lance-format/lance-go#1 ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di lance-format/lance-go
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 80/100
blinklabs-io/gouroboros#3026 ·
I maintainer di solito rispondono entro 1 giorno
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
AvengeMedia/DankMaterialShell#4291 ·
-
[Bug]: autoexport rejects OTEL_*_EXPORTER values that differ only in caseForse già presa @yuminn-k l’ha presa oggi. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 79/100
open-telemetry/opentelemetry-go-contrib#10291 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
podman-container-tools/skopeo#3041 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 85/100
I maintainer di solito rispondono entro 1 giorno