SQL Warnings on Deployment of WAR File to Test Instance
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
Description:
After deploying the WAR file to the test instance, the deployment completes successfully but generates a long list of SQL warnings. These warnings may indicate potential issues with schema creation or conflicts with existing database objects. The full log file is attached for analysis.
Steps to Reproduce:
- Build the WAR file from the repository.
- Deploy the WAR file to the test instance.
- Review the server logs for warnings during the deployment process.
Expected Behavior:
The deployment should succeed without any SQL warnings.
Observed Behavior:
Deployment succeeded, but the server logs contain numerous SQL warnings.
Environment Details:
Deployment Instance: beehive.dataverse.org
Build: v. 6.4 build 1672-82dad99
Database: PostgreSQL
Application Server: [Specify server details]
WAR File Version: v6.4 Development
Sample Warnings:
PER01003: Deployment encountered SQL Exceptions:
PER01000: Got SQLException executing statement "CREATE TABLE EXTERNALTOOLTYPE (ID SERIAL NOT NULL, TYPE VARCHAR(255) NOT NULL, EXTERNALTOOL_ID BIGINT NOT NULL, PRIMARY KEY (ID))": org.postgresql.util.PSQLException: ERROR: relation "externaltooltype" already exists
PER01000: Got SQLException executing statement "CREATE INDEX INDEX_EXTERNALTOOLTYPE_externaltool_id ON EXTERNALTOOLTYPE (externaltool_id)": org.postgresql.util.PSQLException: ERROR: relation "index_externaltooltype_externaltool_id" already exists
PER01000: Got SQLException executing statement "CREATE TABLE DATAVERSETHEME (ID SERIAL NOT NULL, BACKGROUNDCOLOR VARCHAR(255), LINKCOLOR VARCHAR(255), LINKURL VARCHAR(255), LOGO VARCHAR(255), ... PRIMARY KEY (ID))": org.postgresql.util.PSQLException: ERROR: relation "dataversetheme" already exists
PER01000: Got SQLException executing statement "CREATE INDEX INDEX_DATAVERSETHEME_dataverse_id ON DATAVERSETHEME (dataverse_id)": org.postgresql.util.PSQLException: ERROR: relation "index_dataversetheme_dataverse_id" already exists
PER01000: Got SQLException executing statement "CREATE TABLE DATAFILECATEGORY (ID SERIAL NOT NULL, NAME VARCHAR(255) NOT NULL, DATASET_ID BIGINT NOT NULL, PRIMARY KEY (ID))": org.postgresql.util.PSQLException: ERROR: relation "datafilecategory" already exists
Log File:
Deployment Warnings Log.txt
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the attached Deployment Warnings Log.txt and reproduce the WAR deployment against PostgreSQL using the listed v6.4 build and test instance. Compare the CREATE TABLE and CREATE INDEX warnings with the existing database schema to determine whether they are expected or indicate a deployment problem. Done means the cause is identified and deployment no longer produces unexplained SQL warnings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, postgresql
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100