elnur [mailto:t...@cloudera.com]
Sent: Saturday, December 01, 2012 12:17 PM
To: user@oozie.apache.org
Subject: Re: SQL Server as an alternative to derby/mySQL/Oracle?postgreSQL?
In addition, currently Oozie supports derby/mysql/postgres/oracle DBs, it does
not support ms sqlserver.
It will re
In addition, currently Oozie supports derby/mysql/postgres/oracle DBs, it
does not support ms sqlserver.
It will require modifying the persistence.xml file and creating a custom
ORM file for ms sqlserver.
I'd suggest opening a JIRA, I'll be glad to help adding support for another
DB.
Thx
On
I don't think dropping the file into the extracted WAR directory (as
you have done), would be the right approach to do this. Instead, could
you regenerate your WAR file by running oozie-setup.sh after having
made your changes, and then work off of this newly generated oozie.war
file?
On Sat, Dec 1
A little more information, I went back to the original unpacked tar, and added
the file to the source prior to running "mkdistro.sh -DskipTests ", and then
used that updated distro.
Now, I get past the original error and I am getting:
ERROR: Oozie could not be started
REASON: org.apache.oozie.s
Hi,
I currently am using Hive with the metadata store backed in MS SQL Server.
I am now starting to use Oozie, and was wondering if anyone has had success in
changing the store to SQL Server?
The 4 properties that I have changed in oozie-site.xml are:
oozie.service.JPAService.jdbc.d
