Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Lance support: contrib/lance_fdw and the MCP server's Lance tools

Abierto
#2,139 0 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 3 días

@MisterRaindrop ya está trabajando en esto.

Desde el 16/10/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

This tracks the pieces that bring Lance datasets into Apache Cloudberry, as
discussed in #1967 (Making Apache Cloudberry an Agent-Native Analytical
Database). Each PR stands on the one before it, builds and passes its own
tests, and says which of its commits are new.

These PRs follow option B from the 10-10 comment in #1967 (contrib/lance_fdw,
built only with --with-lance). The question of where lance_fdw should live
is still open there; if the community prefers to keep it as a separate project,
I'm happy to close these and continue it outside the tree.

contrib/lance_fdw - a read-only foreign-data wrapper for Lance datasets,
built only with configure --with-lance. It links an installed liblance_c
(the C binding of Lance, written in Rust); no Rust code or crates are added
to this tree. CI builds lance-c from source and runs the suites against a
local S3 gateway (ic-lance-fdw).

  • #2140 lance_fdw: scan Lance datasets, --with-lance, CI
  • #2141 lance_fdw: push qualifiers down to Lance
  • #2142 lance_fdw: push vector Top-K searches down to Lance
  • #2143 lance_fdw: spread a vector search over the segments

mcp-server

  • #2144 mcp-server: read Lance foreign tables and bound query results
  • #2145 mcp-server: write extraction results back (off by default, whitelisted tables only)

The extension starts at version 1.0; until all four lance_fdw PRs are in, the
1.0 install script is still being completed rather than upgraded.

Lenguaje dominante
C
Estrellas
1.4k
Forks
262
Merge medio
4 d 20 h
PR fusionados (30 d)
57

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de apache/cloudberry

Todos los issues de apache/cloudberry

Issues similares

Más issues de C

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.