9c916d12f4
Major release with significant performance improvements and new processing strategy. ## Core Changes - Implemented simple_full_document processing strategy (default) - Full document → LLM approach: 1-2 passes, ~5-6 minutes processing time - Achieved 100% completeness with 2 API calls (down from 5+) - Removed redundant Document AI passes for faster processing ## Financial Data Extraction - Enhanced deterministic financial table parser - Improved FY3/FY2/FY1/LTM identification from varying CIM formats - Automatic merging of parser results with LLM extraction ## Code Quality & Infrastructure - Cleaned up debug logging (removed emoji markers from production code) - Fixed Firebase Secrets configuration (using modern defineSecret approach) - Updated OpenAI API key - Resolved deployment conflicts (secrets vs environment variables) - Added .env files to Firebase ignore list ## Deployment - Firebase Functions v2 deployment successful - All 7 required secrets verified and configured - Function URL: https://api-y56ccs6wva-uc.a.run.app ## Performance Improvements - Processing time: ~5-6 minutes (down from 23+ minutes) - API calls: 1-2 (down from 5+) - Completeness: 100% achievable - LLM Model: claude-3-7-sonnet-latest ## Breaking Changes - Default processing strategy changed to 'simple_full_document' - RAG processor available as alternative strategy 'document_ai_agentic_rag' ## Files Changed - 36 files changed, 5642 insertions(+), 4451 deletions(-) - Removed deprecated documentation files - Cleaned up unused services and models This release represents a major refactoring focused on speed, accuracy, and maintainability.
50 lines
1.3 KiB
SQL
50 lines
1.3 KiB
SQL
-- Temporary workaround: Drop FK, create job, recreate FK
|
|
-- This is safe because we know the document exists (verified via service client)
|
|
-- The FK will be recreated to maintain data integrity
|
|
|
|
-- Step 1: Drop FK constraint temporarily
|
|
ALTER TABLE processing_jobs
|
|
DROP CONSTRAINT IF EXISTS processing_jobs_document_id_fkey;
|
|
|
|
-- Step 2: Create the job
|
|
INSERT INTO processing_jobs (
|
|
document_id,
|
|
user_id,
|
|
status,
|
|
attempts,
|
|
max_attempts,
|
|
options,
|
|
created_at
|
|
) VALUES (
|
|
'78359b58-762c-4a68-a8e4-17ce38580a8d'::uuid,
|
|
'B00HiMnleGhGdJgQwbX2Ume01Z53',
|
|
'pending',
|
|
0,
|
|
3,
|
|
'{"strategy": "document_ai_agentic_rag"}'::jsonb,
|
|
NOW()
|
|
)
|
|
RETURNING id, document_id, status, created_at;
|
|
|
|
-- Step 3: Recreate FK constraint (with explicit schema)
|
|
ALTER TABLE processing_jobs
|
|
ADD CONSTRAINT processing_jobs_document_id_fkey
|
|
FOREIGN KEY (document_id)
|
|
REFERENCES public.documents(id)
|
|
ON DELETE CASCADE;
|
|
|
|
-- Step 4: Verify job was created
|
|
SELECT
|
|
id as job_id,
|
|
document_id,
|
|
status as job_status,
|
|
created_at
|
|
FROM processing_jobs
|
|
WHERE document_id = '78359b58-762c-4a68-a8e4-17ce38580a8d'::uuid
|
|
ORDER BY created_at DESC;
|
|
|
|
-- Note: The FK constraint will validate existing data when recreated
|
|
-- If the document doesn't exist, the ALTER TABLE will fail at step 3
|
|
-- But if it succeeds, we know the document exists and the job is valid
|
|
|