Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1261111

Summary: RT-Gov 2.x database schema difference from 1.x schema
Product: [JBoss] JBoss Fuse Service Works 6 Reporter: Julian Coleman <jcoleman>
Component: RT GovernanceAssignee: Nobody <nobody>
Status: CLOSED UPSTREAM QA Contact: Matej Melko <mmelko>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 6.2.0CC: ganandan, soa-p-jira
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-02-10 03:48:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Julian Coleman 2015-09-08 15:24:00 UTC
RT-Gov 2.x has added the column:

    internal boolean,

in the `RTGOV_ACTIVITIES' table.  This is problematic:

  a change from the 1.x schema
  boolean is only supported by H2, MySQL, and PostgreSQL

Comment 1 Gary Brown 2015-09-09 13:12:18 UTC
Proposal is to remove this field from the db schema, as it is only really used within ElasticSearch/Kibana to filter out internal services.

The benefit being that the db schema will not change, so no update/migration scripts required.

Comment 2 JBoss JIRA Server 2015-09-14 08:34:23 UTC
Gary Brown <gary> updated the status of jira RTGOV-666 to Resolved

Comment 3 Gomathi Anandan 2015-09-14 15:07:02 UTC
This issue has been resolved by engineering.Acking it for this release.

Comment 7 Red Hat Bugzilla 2025-02-10 03:48:09 UTC
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.