Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

[Bug]: Preserve autoentity-generated entities in multi-source MCP runtime configuration

未关闭
#3,729 0 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

@RubenCerna2079 已经在做这个了。

开始于 2026年7月17日。

评估

这个 Issue 还没有评估数据。

描述

2.x auto-config bug known-issue triage
What happened?

When multiple child configurations use SQL autoentities with MCP enabled, DAB discovers entities during child/provider initialization but describe_entities returns NoEntitiesConfigured from the final merged runtime configuration. A parent with one child and each child tested independently work, while a parent with two or more children reproduces the failure.

Expected behavior: all generated entities from every child configuration should be present in the shared runtime configuration and returned by describe_entities, with each entity mapped to its originating data source.

Observed behavior: startup completes successfully and dab validate reports discovered entities, but MCP sees no usable entities. The issue appears to occur while propagating generated autoentities from per-child/per-datasource metadata providers into the shared root RuntimeConfig.Entities collection used by MCP.

This is a child investigation item for https://github.com/Azure/data-api-builder/issues/3711. Please verify the runtime merge sequence, generated entity collection, and entity-to-data-source mappings across two or more child configurations.

Version

2.0.9

What database are you using?

Azure SQL

What hosting model are you using?

Local (including CLI)

Which API approach are you accessing DAB through?

MCP

Relevant log output
Startup completes with `Successfully completed runtime initialization`, but `tools/call` for `describe_entities` returns `NoEntitiesConfigured` after using a parent config with two or more child configs containing `autoentities`.
Code of Conduct
  • I agree to follow this project's Code of Conduct
主要语言
C#
星标
1.5k
派生
372
平均合并
9 天 1 小时
30 天内合并 PR
13

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

Azure/data-api-builder 的其他 Issue

查看 Azure/data-api-builder 的全部 Issue

相似的 Issue

更多 C# Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。