Changelog
Proof Service
Changelog 2023-09-06 by @Nyk Ma
New Features
- Added support platforms:
- Introduced proof expiration mechanism: proof will be revalidated only if the record is outdated
- Display current runtime information in the /healthz endpoint
Updates
- Updated code related to Slack integration
- Split read and write database connections
Platform::Twitter: Record the numeric ID of Twitter users (inAltIDfield)Platform::Twitter: Use twitter’s GraphQL API for Twitter binding validationPlatform::Twitter: Retry several times when calling twitter GraphQL API- To overcome temporarily request fails
GET /v1/proof: now shows 40 records per page
Fixes
- Fix some issue with headless browser function
- Disable auto migration in Lambda environment to boost cold start duration when a new lambda instance starts
Relation Service
Changelog 2023-09-06 by @Zella Zhong
Switched GraphDB Engine to TigerGraph
- Why: To handle rising data volumes and enable advanced analytics capabilities
- Impact: Improved query performance by 70%, added new query functionalities, and optimized data fetching
- Features:
- GSQL migrations and [tdb] configuration
- New query functionalities like
neighbors(),neighbors_with_source(),domain(), etc - Action Required: Users may need to update configurations and be aware of deprecated ArangoDB-related code
New Features
- GSQL Client Tweaks: Optimized GSQL interactions for faster migrations and queries
- Delete Vertex and Edge Method: Added for handling outdated data
Improvements
- Fetch All Procedure: Enhanced to support parallel querying and timeout settings
- Access Management: Improved security for graph and tokens
- Data Sources: Expanded and updated DataSource enum
Bug Fixes
Removals
Infrastructure & Maintenance
- Updated dependencies and configurations
- Merged changes into the
graphdb/tigergraphbranch and set up CI