I think this is a doc issue when it comes to DB like mysql. But, it is a real issue for sql server which oozie also supports. In sql server, varchar or text don't support unicode and by default, openJPA mapping tool maps "String" into "varchar(255)" instead of "nvarchar" or "ntext". Is there a way for openJPA to not map "String" into "Varchar" during table creation? If not, we need to do some specila handling for sql server in oozieDBCLI.
On Tuesday, August 12, 2014 6:39 AM, Alejandro Abdelnur <[email protected]> wrote: So, it seems it is a JVM and DB configuration issue, right? It would be great to verify this is the case and add the necessary config steps to the documentation. thx On Mon, Aug 11, 2014 at 2:03 PM, bowen zhang <[email protected]> wrote: I think I figured out this issue. For oozie to support unicode in path name, the JAVA_TOOL_OPTIONS in the JVM needs to use an encoding method that supports unicode. And the oozie DB needs to use an encoding method that's consistent with the JVM. By default, mysql, for example, uses "latin1" if running "create database oozie;". This won't work since "latin1" only supports Western characters. > > > > >On Friday, August 8, 2014 7:06 PM, bowen zhang <[email protected]> wrote: > > > >here is an example: >cat job.properties: >nameNode=hdfs://localhost:9000 >jobTracker=localhost:8032 >queueName=default >examplesRoot=examples > >oozie.wf.application.path=${nameNode}/user/${user.name}/${examplesRoot}/apps/map-reduceć–‡ >outputDir=map-reduce > > > >On Friday, August 8, 2014 6:55 PM, Alejandro Abdelnur <[email protected]> >wrote: > > > >hey bowen, it would help to know exactly where do you see issues, a simple wf >showing the issue would be great > >Alejandro >(phone typing) > > >> On Aug 8, 2014, at 18:12, bowen zhang <[email protected]> >> wrote: >> >> Hi guys, >> I recently discovered a hole in oozie implementation where oozie breaks when >> having hdfs app_path with unicode. If my app_path contains non-ascii >> characters like Chinese words, the DB and server side will not retrieve it >> correctly. Do we have strict utf-8 encoding throughout oozie? Any thoughts >> on this? >> Bowen -- Alejandro
