# Description
Implement Pie Chart visualization support in dashboard components.
This PR adds pie chart visualization capability to the dashboard,
allowing users to:
- Render pie charts in the chat_dashboard mode
- Preview pie charts in the chat_dashboard editor mode
## Implementation Details
- Added new file: `web/components/chart/pie-chart.tsx` that implements
pie chart rendering logic using G2
- Modified `web/components/chart/index.tsx` to integrate the pie chart
component into the dashboard chart rendering flow
- Added animation effects, hover interactions, and improved legend
display
- Fixed interaction bugs to ensure smooth visualization
# How Has This Been Tested?
Testing procedure included:
1. Creating datasets with category-based data suitable for pie charts
2. Verifying pie chart visualization in chat_dashboard mode
3. Confirming preview functionality works correctly in the editor mode
4. Testing interactions: hover effects, animations, and legend display
All tests confirm the feature works as expected with proper
visualization of categorical data proportions.
# Snapshots:
# Checklist:
- [x] My code follows the style guidelines of this project
- [x] I have already rebased the commits and make the commit message
conform to the project standard.
- [x] I have performed a self-review of my own code
- [x] I have commented my code, particularly in hard-to-understand areas
- [x] I have made corresponding changes to the documentation
- [x] Any dependent changes have been merged and published in downstream
modules
Fixes#2708
- Refactor task execution to improve concurrency control
- Implement batch processing for vector deletion in Chroma store
# Description
1 ,When chunk a knowledge base file, if there are too many chunks ,
using asyncio.gather(*tasks) will cause the CPU to freeze
2 , When using the Chroma vector database, if the one-time deletion of
embedding documents ids exceeds 5461, it will fail
# How Has This Been Tested?
# Snapshots:
Include snapshots for easier review.
# Checklist:
- [x] My code follows the style guidelines of this project
- [x] I have already rebased the commits and make the commit message
conform to the project standard.
- [x] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [ ] Any dependent changes have been merged and published in downstream
modules
- Add reranking support to improve the quality of retrieved chunks
- Implement RerankEmbeddingFactory and RerankEmbeddingsRanker
- Update RetrieverResource to use reranking when configured
- Modify retrieve method to apply reranking if needed
The logic for determining whether to use reranking and setting the `top_k` value now depends on the `app_config` instead of directly using `CFG.RERANK_MODEL` and `CFG.RERANK_TOP_K`. This change ensures that the application's specific configuration settings are respected.
Close#2595
# Description
fix hybrid memory milvus create collection bug
# How Has This Been Tested?
switch milvus for hybrid storage type.
# Snapshots:
Include snapshots for easier review.
# Checklist:
- [ ] My code follows the style guidelines of this project
- [ ] I have already rebased the commits and make the commit message
conform to the project standard.
- [ ] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [ ] Any dependent changes have been merged and published in downstream
modules
