Skip to content

Fix PostgreSQL array handling in JdbcFeedSource#352

Closed
ksrihari09 wants to merge 14 commits intofeature_openapifrom
fix/postgresql-array-handling
Closed

Fix PostgreSQL array handling in JdbcFeedSource#352
ksrihari09 wants to merge 14 commits intofeature_openapifrom
fix/postgresql-array-handling

Conversation

@ksrihari09
Copy link

  • Add null-safe handling for categories array to prevent PSQLException
  • Handle cases where PostgreSQL returns null arrays gracefully
  • Fix POM version mismatch (1.2.35 -> 1.2.36-SNAPSHOT)
  • Resolves DataIntegrityViolationException: No results were returned by the query

The original error occurred when PostgreSQL JDBC driver couldn't handle null array types in the categories column. This fix adds proper null checks before attempting to extract array contents.

- Add null-safe handling for categories array to prevent PSQLException
- Handle cases where PostgreSQL returns null arrays gracefully
- Fix POM version mismatch (1.2.35 -> 1.2.36-SNAPSHOT)
- Resolves DataIntegrityViolationException: No results were returned by the query

The original error occurred when PostgreSQL JDBC driver couldn't handle
null array types in the categories column. This fix adds proper null
checks before attempting to extract array contents.
- Update all module versions from 1.2.35/1.2.36-SNAPSHOT to 1.2.36
- Includes PostgreSQL array handling fix for production deployment
- Ready for artifact release to GitHub Packages
- Update all module versions to 1.2.35 (following parent-1.2.34)
- Includes PostgreSQL array handling fix for production deployment
- Ready for artifact release to GitHub Packages
- Fix GitHub Packages repository URLs (remove .git suffix)
- Remove duplicate dynamoDB_adapters dependency from atomhopper/pom.xml
- Update snapshot repository ID to match main repository for consistency
- Change from self-hosted to ubuntu-latest runner
- Add GitHub Packages authentication for Docker build
- Update Dockerfile to use GitHub Packages with authentication
- Add AWS credentials configuration step
- Update version to 1.2.35 in Docker configuration
- Add comprehensive error handling and logging
- Update Dockerfile COPY command to use correct path for start.sh
- Build context is root directory, so need to specify docker/start.sh
- Add verbose curl output to see authentication and response details
- Add file type checking and content inspection
- Add validation before attempting to unzip
- Show actual content if download fails
- Use absolute path in CMD instruction: /opt/atomhopper/start.sh
- Restore GitHub Packages authentication setup
- Update version to 1.2.35
- Add verification of start.sh file permissions
- Ensure proper file copying and executable permissions
- Add -L flag to curl to follow redirects from GitHub Packages
- GitHub Packages returns 302 redirect to AWS S3 for actual file download
- Simplify debugging output while keeping essential verification
- This should now properly download the WAR file instead of HTML redirect page
@ksrihari09 ksrihari09 closed this Sep 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant