You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oodt.apache.org by "Chris A. Mattmann (JIRA)" <ji...@apache.org> on 2011/06/19 06:29:47 UTC
[jira] [Created] (OODT-230) Curator adds escaped sequenced spaces
when reading extractorBinPath tag from extractor config files
Curator adds escaped sequenced spaces when reading extractorBinPath tag from extractor config files
---------------------------------------------------------------------------------------------------
Key: OODT-230
URL: https://issues.apache.org/jira/browse/OODT-230
Project: OODT
Issue Type: Bug
Components: curator
Reporter: Joshua Garcia
Assignee: Chris A. Mattmann
Fix For: 0.4
If a config file is set up as the following, which is shown on the cas-curator user guide:
{noformat}
[joshuaga@jpl-esg mp3extractor]$ cat mp3PythonExtractor.config
{noformat}
{code:xml}
<?xml version="1.0" encoding="UTF-8"?>
<cas:externextractor xmlns:cas="http://oodt.jpl.nasa.gov/1.0/cas">
<exec workingDir="">
<extractorBinPath>
/home/joshuaga/extractors/mp3extractor/mp3PythonExtractor.py
</extractorBinPath>
<args>
<arg isDataFile="true"/>
</args>
</exec>
</cas:externextractor>
{code}
tomcat's catalina.out log file can have a warning such as:
{noformat}
WARNING: IOException running met extraction: commandLine: [\ /home/joshuaga/extractors/mp3extractor/mp3PythonExtractor.py\ \ \ \ \ \ \ /home/joshuaga/staging/products/mp3/Bach-SuiteNo2.mp3 ]: Message: java.io.IOException: \ /home/joshuaga/extractors/mp3extractor/mp3PythonExtractor.py\ \ \ \ \ \ \ : not found
{noformat}
Which shows that the command being run when using the extractor is adding spaces with escape sequences which gives the not found error shown.
The workaround is simply:
{code:xml}
<?xml version="1.0" encoding="UTF-8"?>
<cas:externextractor xmlns:cas="http://oodt.jpl.nasa.gov/1.0/cas">
<exec workingDir="">
<extractorBinPath>/home/joshuaga/extractors/mp3extractor/mp3PythonExtractor.py</extractorBinPath>
<args>
<arg isDataFile="true"/>
</args>
</exec>
</cas:externextractor>
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OODT-230) Curator adds escaped sequenced spaces
when reading extractorBinPath tag from extractor config files
Posted by "Chris A. Mattmann (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris A. Mattmann updated OODT-230:
-----------------------------------
- push out to 0.5
> Curator adds escaped sequenced spaces when reading extractorBinPath tag from extractor config files
> ---------------------------------------------------------------------------------------------------
>
> Key: OODT-230
> URL: https://issues.apache.org/jira/browse/OODT-230
> Project: OODT
> Issue Type: Bug
> Components: curator
> Reporter: Joshua Garcia
> Assignee: Chris A. Mattmann
> Fix For: 0.5
>
>
> If a config file is set up as the following, which is shown on the cas-curator user guide:
> {noformat}
> [joshuaga@jpl-esg mp3extractor]$ cat mp3PythonExtractor.config
> {noformat}
> {code:xml}
> <?xml version="1.0" encoding="UTF-8"?>
> <cas:externextractor xmlns:cas="http://oodt.jpl.nasa.gov/1.0/cas">
> <exec workingDir="">
> <extractorBinPath>
> /home/joshuaga/extractors/mp3extractor/mp3PythonExtractor.py
> </extractorBinPath>
> <args>
> <arg isDataFile="true"/>
> </args>
> </exec>
> </cas:externextractor>
> {code}
> tomcat's catalina.out log file can have a warning such as:
> {noformat}
> WARNING: IOException running met extraction: commandLine: [\ /home/joshuaga/extractors/mp3extractor/mp3PythonExtractor.py\ \ \ \ \ \ \ /home/joshuaga/staging/products/mp3/Bach-SuiteNo2.mp3 ]: Message: java.io.IOException: \ /home/joshuaga/extractors/mp3extractor/mp3PythonExtractor.py\ \ \ \ \ \ \ : not found
> {noformat}
> Which shows that the command being run when using the extractor is adding spaces with escape sequences which gives the not found error shown.
> The workaround is simply:
> {code:xml}
> <?xml version="1.0" encoding="UTF-8"?>
> <cas:externextractor xmlns:cas="http://oodt.jpl.nasa.gov/1.0/cas">
> <exec workingDir="">
> <extractorBinPath>/home/joshuaga/extractors/mp3extractor/mp3PythonExtractor.py</extractorBinPath>
> <args>
> <arg isDataFile="true"/>
> </args>
> </exec>
> </cas:externextractor>
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OODT-230) Curator adds escaped sequenced spaces
when reading extractorBinPath tag from extractor config files
Posted by "Chris A. Mattmann (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris A. Mattmann updated OODT-230:
-----------------------------------
Fix Version/s: (was: 0.4)
0.5
- push to 0.5
> Curator adds escaped sequenced spaces when reading extractorBinPath tag from extractor config files
> ---------------------------------------------------------------------------------------------------
>
> Key: OODT-230
> URL: https://issues.apache.org/jira/browse/OODT-230
> Project: OODT
> Issue Type: Bug
> Components: curator
> Reporter: Joshua Garcia
> Assignee: Chris A. Mattmann
> Fix For: 0.5
>
>
> If a config file is set up as the following, which is shown on the cas-curator user guide:
> {noformat}
> [joshuaga@jpl-esg mp3extractor]$ cat mp3PythonExtractor.config
> {noformat}
> {code:xml}
> <?xml version="1.0" encoding="UTF-8"?>
> <cas:externextractor xmlns:cas="http://oodt.jpl.nasa.gov/1.0/cas">
> <exec workingDir="">
> <extractorBinPath>
> /home/joshuaga/extractors/mp3extractor/mp3PythonExtractor.py
> </extractorBinPath>
> <args>
> <arg isDataFile="true"/>
> </args>
> </exec>
> </cas:externextractor>
> {code}
> tomcat's catalina.out log file can have a warning such as:
> {noformat}
> WARNING: IOException running met extraction: commandLine: [\ /home/joshuaga/extractors/mp3extractor/mp3PythonExtractor.py\ \ \ \ \ \ \ /home/joshuaga/staging/products/mp3/Bach-SuiteNo2.mp3 ]: Message: java.io.IOException: \ /home/joshuaga/extractors/mp3extractor/mp3PythonExtractor.py\ \ \ \ \ \ \ : not found
> {noformat}
> Which shows that the command being run when using the extractor is adding spaces with escape sequences which gives the not found error shown.
> The workaround is simply:
> {code:xml}
> <?xml version="1.0" encoding="UTF-8"?>
> <cas:externextractor xmlns:cas="http://oodt.jpl.nasa.gov/1.0/cas">
> <exec workingDir="">
> <extractorBinPath>/home/joshuaga/extractors/mp3extractor/mp3PythonExtractor.py</extractorBinPath>
> <args>
> <arg isDataFile="true"/>
> </args>
> </exec>
> </cas:externextractor>
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira