I have two questions about the Databases in MH:
1. what is the maximum capacity of the embedded H2 DB, so the usage of the
standalone DB server is necessary?
2. at the end of December I saw a discussion (see below) about a problem with
two recommended (MySQL, and PostgreSQL) databases,
and I wonder if these is now sorted out ?
Many thanks,
Leslaw
Begin forwarded message:
> From: Hank Magnuski <[email protected]>
> Date: December 18, 2011 11:17:04 PM GMT
> To: Matterhorn Users <[email protected]>
> Subject: Re: [Matterhorn-users] Database woes in Matterhorn
> Reply-To: Matterhorn Users <[email protected]>
>
> This problem was fixed by adding ORGANIZATION to MH_ROLE
>
> `ORGANIZATION` varchar(255) collate utf8_unicode_ci default NULL,
>
> I think the offending bundle was:
>
> matterhorn-userdirectory-jpa-1.3-rc4.jar
>
> I don't think anyone else in the community is running with multi-tenancy
> enabled. I suspect many of the problems I'm seeing are due to issues related
> to this feature which was introduced in 1.3. By not using an Apache proxy one
> is more or less forced to enable multi-tenancy and run into these errors.
>
> Hank
>
> On Sun, Dec 18, 2011 at 1:57 PM, Greg Logan <[email protected]> wrote:
> On 12/17/2011 2:14 PM, Hank Magnuski wrote:
> > After repairing a few obvious column missing errors, I get this error
> > and have no idea how to fix the DB for this message:
>
> Which bundle(s) are failing? I cut the RC and ran the integration tests
> both before and after. None of these issues have appeared for me.
>
> G
>
> > 14:59:43 ERROR (AbstractFaultChainInitiatorObserver:101) - Error
> > occurred during error handling, give up!
> > org.apache.cxf.interceptor.Fault:
> > Internal Exception:
> > com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown
> > column 't1.ORGANIZATION' in 'where clause'
> > Error Code: 1054
> > Call: SELECT DISTINCT t1.ROLE FROM MH_USER t0, MH_ROLE t1 WHERE
> > ((t1.ORGANIZATION = t0.ORGANIZATION) AND (t1.USERNAME = t0.USERNAME))
> > Query: ReportQuery(name="roles" referenceClass=JpaUser sql="SELECT
> > DISTINCT t1.ROLE FROM MH_USER t0, MH_ROLE t1 WHERE ((t1.ORGANIZATION =
> > t0.ORGANIZATION) AND (t1.USERNAME = t0.USERNAME))")
> > at
> > org.apache.cxf.service.invoker.AbstractInvoker.createFault(AbstractInvoker.java:155)
> > at
> > org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:121)
> > at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:133)
> > at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:82)
> >
> >
> > On Sat, Dec 17, 2011 at 10:12 AM, Greg Logan <[email protected]
> > <mailto:[email protected]>> wrote:
> >
> > On 12/17/2011 11:28 AM, Christopher Brooks wrote:
> > > Hey hank,
> > >
> > > The autogeneration of ddl does not work reliably. The mysql
> > scripts are the most up to date, and there was a resolution on list
> > to reduce our coverage just to one script (the mysql one) to help
> > eliminate these issues, so the postgres scripts should be removed
> > from future releases. Instead, we'll advertise in our release docs
> > any community contributed scripts for non mysql dbs.
> > >
> > > So, I'd try with mysql right now, and autogen off (there were
> > significant db naming convention changes in this last rc).
> >
> > Either something changed and no one told me, or you missed that the
> > review is just a patch set :)
> >
> > Hank, autogen should work fine on an empty DB, but I imagine it might
> > complain on a DB with existing tables since some things may have
> > changed. The large refactoring Chris is talking about is *not* in rc4.
> > For what it's worth, my day-to-day dev environment, as well as the test
> > clusters we have available (testadmin.usask.ca
> > <http://testadmin.usask.ca> and
> > testallinone.usask.ca <http://testallinone.usask.ca>) are all
> > running with ddl-autogen turned on
> > against mysql and I haven't seen any issues related to that at all. THe
> > ddl scripts are currently known to be broken, so please don't use them
> > yet! This is what will be addressed with the DB refactoring (see
> > MH-8335 for details).
> >
> > G
>
> _______________________________________________
> Matterhorn-users mailing list
> [email protected]
> http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
_______________________________________________
Matterhorn-users mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
