What the data for this category looks like
Traditional Chinese medicine enterprise financial report data comes from public annual, semi-annual, and quarterly reports of listed companies disclosed by the Shanghai and Shenzhen stock exchanges, plus annual operation announcements released by enterprises themselves. The data update schedule is one annual report per year, two semi-annual reports per year, and one quarterly report per quarter. Temporary announcements related to herbal medicine procurement and production capacity are also included. Most documents are standard PDF files, containing main financial statements and management discussion and analysis sections. Besides common financial fields, they include exclusive fields such as herbal medicine procurement amount, decoction pieces production capacity, and herbal medicine inventory. Common units are ten thousand yuan, tons, and pieces.
What constraints these characteristics impose on deployment and upgrade
Multiple update frequencies require scheduled synchronization tasks to be configured during deployment. This ensures quarterly and semi-annual reports are added to the knowledge base promptly. Exclusive herbal medicine and production capacity fields require the parsing module to support custom extraction rules. This prevents generic parsing from missing key information. The high proportion of long-text management discussion and analysis sections increases parsing timeout risk. Adjust the parsing timeout threshold during deployment. Non-standard formats of temporary announcements require the upgrade process to support announcement PDFs with different layouts. This avoids parsing failures. Large-volume financial report PDFs require increased upload limits. This prevents files from being blocked.
Configuration Settings
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
PARSE_FILE_TIMEOUT_SECONDS | 600 seconds | Traditional Chinese medicine financial report PDFs contain long-text sections, with longer parsing times than generic documents. This avoids early termination of parsing |
UPLOAD_FILE_MAX_SIZE | 1000 MB | Single annual financial report PDFs often include multiple pages of financial statements and operational details, requiring support for large file uploads |
Chunk Length | 800–1200 characters | Exclusive fields for traditional Chinese medicine financial reports are often scattered across continuous paragraphs. This chunk range preserves contextual relevance of the fields |
Retrieval Count | Top 8–12 entries | Financial report analysis requires covering multi-dimensional data. This range balances retrieval completeness and inference efficiency |
PARSE_SPLIT_MODE | Split by semantic meaning | Avoid splitting by fixed character count, which could damage the semantic integrity of exclusive fields such as herbal medicine procurement and production capacity |
LLM_API_BASE | Set based on actual testing | Adapt to the interface address of locally deployed large models, meeting deployment requirements for environments without public network access |
The parameter values provided on this page are common recommended starting points for configuration. Actual values are affected by material format, data volume, and business rules. Specific issues require individual analysis. It is recommended to test on your own samples before finalizing settings.
Three Common Configuration Mistakes
- Issue: File parsing fails, with logs indicating a
splitparameter exception. Cause: The chunk configuration was not adjusted for the long-text characteristics of traditional Chinese medicine financial reports, triggering the parsing module's chunk validation rules. - Issue: In the 4.9.0 Docker deployment version, no valid text is returned after file parsing. Cause: The mount path between the file parsing module and the main service was not configured correctly, causing parsing results to fail to sync to the knowledge base.
- Issue: After upgrading to version 4.9.0, the document parsing function cannot be enabled normally. Cause: The open-source version permission configuration was not confirmed, and a feature exclusive to the commercial version was accidentally enabled.
How to Confirm Proper Configuration
- Upload a single annual financial report PDF for a traditional Chinese medicine enterprise. Check if the parsing result covers exclusive business fields such as herbal medicine procurement and production capacity, and confirm that the chunk configuration does not damage semantic integrity.
- Verify the value of the file parsing timeout configuration. Ensure it matches the time required for long-text parsing, and check for no early termination error logs.
- Test the local large model call process. Confirm that the interface address configuration is correct, and check for no connection error prompts.
- View the execution logs of scheduled sync tasks. Confirm that financial report data can be automatically synced to the knowledge base at the preset schedule, and check for no timeout or failure records.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-09-14.