Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

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

Aberta
  • Algo errado?
#2,139 5 comentários 0 reações 1 responsável Ver no GitHub

Mantenedores costumam responder em até 3 dias

@MisterRaindrop já está trabalhando nisso.

Desde 16/10/2026.

Avaliação

Esta issue ainda não foi avaliada.

Descrição

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.

Linguagem predominante
C
Estrelas
1.4k
Forks
262
Merge médio
4d 20h
PRs com merge (30d)
57

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de apache/cloudberry

Todas as issues de apache/cloudberry

Issues semelhantes

Mais issues de C

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.