You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oodt.apache.org by "Hardman, Sean H (388J)" <se...@jpl.nasa.gov> on 2012/02/21 03:30:09 UTC

Issue with query_tool when all product types are not populated

I first noticed this behavior in release 0.3 and just reaffirmed it in a latest and greatest build of 0.4-SNAPSHOT. To the best of my knowledge, this was not the case in previous versions. When querying a File Manager instance with a Lucene Catalog on the back end, the query_tool will throw an exception unless there is a product ingested for each product type listed in the policy (see the stack trace below).

I assume I am not the first person to notice this behavior. Is this worthy of a JIRA issue?

Thanks,
Sean


bash-3.2$ ./query_tool --url ${FILEMGR_URL} --sql -query "SELECT * FROM *"
Feb 20, 2012 5:52:26 PM org.apache.oodt.cas.filemgr.catalog.LuceneCatalog paginateQuery
WARNING: Query: [q=] for Product Type: [urn:pds:CatalogObject] returned no results
java.lang.NullPointerException
at org.apache.oodt.cas.filemgr.system.XmlRpcFileManager.complexQuery(XmlRpcFileManager.java:602)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.xmlrpc.Invoker.execute(Invoker.java:130)
at org.apache.xmlrpc.XmlRpcWorker.invokeHandler(XmlRpcWorker.java:84)
at org.apache.xmlrpc.XmlRpcWorker.execute(XmlRpcWorker.java:146)
at org.apache.xmlrpc.XmlRpcServer.execute(XmlRpcServer.java:139)
at org.apache.xmlrpc.XmlRpcServer.execute(XmlRpcServer.java:125)
at org.apache.xmlrpc.WebServer$Connection.run(WebServer.java:761)
at org.apache.xmlrpc.WebServer$Runner.run(WebServer.java:642)
at java.lang.Thread.run(Thread.java:680)
org.apache.xmlrpc.XmlRpcException: java.lang.Exception: org.apache.oodt.cas.filemgr.structs.exceptions.CatalogException: Failed to perform complex query : null
at org.apache.xmlrpc.XmlRpcClientResponseProcessor.decodeException(XmlRpcClientResponseProcessor.java:104)
at org.apache.xmlrpc.XmlRpcClientResponseProcessor.decodeResponse(XmlRpcClientResponseProcessor.java:71)
at org.apache.xmlrpc.XmlRpcClientWorker.execute(XmlRpcClientWorker.java:73)
at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:194)
at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:185)
at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:178)
at org.apache.oodt.cas.filemgr.system.XmlRpcFileManagerClient.complexQuery(XmlRpcFileManagerClient.java:974)
at org.apache.oodt.cas.filemgr.tools.QueryTool.performSqlQuery(QueryTool.java:252)
at org.apache.oodt.cas.filemgr.tools.QueryTool.main(QueryTool.java:242)
Exception in thread "main" org.apache.oodt.cas.filemgr.structs.exceptions.CatalogException: java.lang.Exception: org.apache.oodt.cas.filemgr.structs.exceptions.CatalogException: Failed to perform complex query : null
at org.apache.oodt.cas.filemgr.system.XmlRpcFileManagerClient.complexQuery(XmlRpcFileManagerClient.java:980)
at org.apache.oodt.cas.filemgr.tools.QueryTool.performSqlQuery(QueryTool.java:252)
at org.apache.oodt.cas.filemgr.tools.QueryTool.main(QueryTool.java:242)


Re: Issue with query_tool when all product types are not populated

Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Thanks Sheryl, you rock!

Cheers,
Chris

On Feb 23, 2012, at 12:48 AM, Sheryl John wrote:

> I've added an issue for this :
> https://issues.apache.org/jira/browse/OODT-384
> 
> Thanks,
> 
> On Wed, Feb 22, 2012 at 9:38 PM, Mattmann, Chris A (388J) <
> chris.a.mattmann@jpl.nasa.gov> wrote:
> 
>> Thanks for the case Sheryl. Would you mind filing a JIRA issue for 0.5 to
>> investigate this?
>> 
>> Cheers,
>> Chris
>> 
>> On Feb 22, 2012, at 3:49 PM, Sheryl John wrote:
>> 
>>> Hi,
>>> 
>>> I've experienced the same today while working with 0.4-snapshot (not
>> latest
>>> build ) and also the query does not seem to accept '*' for the elements.
>>> For the following use case:
>>> 
>>> ./filemgr-client --url http://localhost:9000 -op -sql -query "SELECT *
>> FROM
>>> CernerLocations"
>>> 
>>> The stack trace:
>>> 
>>> Feb 22, 2012 2:36:52 PM
>>> org.apache.oodt.cas.filemgr.system.XmlRpcFileManager complexQuery
>>> INFO: Query returned 2 results
>>> org.apache.xmlrpc.XmlRpcException: org.apache.xmlrpc.XmlRpcException:
>> null
>>> values not supported by XML-RPC
>>> at
>>> 
>> org.apache.xmlrpc.XmlRpcClientResponseProcessor.decodeException(XmlRpcClientResponseProcessor.java:104)
>>> at
>>> 
>> org.apache.xmlrpc.XmlRpcClientResponseProcessor.decodeResponse(XmlRpcClientResponseProcessor.java:71)
>>> at
>> org.apache.xmlrpc.XmlRpcClientWorker.execute(XmlRpcClientWorker.java:73)
>>> at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:194)
>>> at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:185)
>>> at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:178)
>>> at
>>> 
>> org.apache.oodt.cas.filemgr.system.XmlRpcFileManagerClient.complexQuery(XmlRpcFileManagerClient.java:974)
>>> at
>>> 
>> org.apache.oodt.cas.filemgr.cli.action.AbstractQueryCliAction.execute(AbstractQueryCliAction.java:75)
>>> at
>> org.apache.oodt.cas.cli.CmdLineUtility.execute(CmdLineUtility.java:296)
>>> at org.apache.oodt.cas.cli.CmdLineUtility.run(CmdLineUtility.java:179)
>>> at
>>> 
>> org.apache.oodt.cas.filemgr.system.XmlRpcFileManagerClient.main(XmlRpcFileManagerClient.java:1307)
>>> ERROR: Failed to perform sql query : sortBy 'null', outputFormat 'null',
>>> and delimiter '
>>> ', filterAlgor 'null', startDateTimeMetKey 'null', endDateTimeMetKey
>>> 'null', priorityMetKey 'null', null' : org.apache.xmlrpc.XmlRpcException:
>>> null values not supported by XML-RPC
>>> 
>>> 
>>> But if add the elements' names in the query I get the desired query
>> results.
>>> 
>>> ./filemgr-client --url http://palmer:9000 -op -sql -query "SELECT
>>> CAS.ProductName,PID FROM CernerLocations"
>>> 
>>> Feb 22, 2012 2:45:22 PM
>>> org.apache.oodt.cas.filemgr.system.XmlRpcFileManager complexQuery
>>> INFO: Query returned 2 results
>>> blah_xx.csv,xxxx
>>> blah_yy.csv,yyyy
>>> 
>>> 
>>> 
>>> 
>>> On Tue, Feb 21, 2012 at 1:38 PM, Mattmann, Chris A (388J) <
>>> chris.a.mattmann@jpl.nasa.gov> wrote:
>>> 
>>>> Hey Sean,
>>>> 
>>>> Thanks for the FYI. OK, so it's not a regression, but it sounds worthy
>> of
>>>> a JIRA
>>>> issue. I'd say go for it and let's investigate the fix, even if it means
>>>> porting it
>>>> out of wengine.
>>>> 
>>>> Cheers,
>>>> Chris
>>>> 
>>>> On Feb 21, 2012, at 10:23 AM, Hardman, Sean H (388J) wrote:
>>>> 
>>>>> Hey Chris,
>>>>> 
>>>>> Yes, the identical behavior can be seen 0.3, I am just slow to complain
>>>>> about it. I haven't tried 0.2, but this query does work successfully in
>>>>> the wengine-branch version of the FM. For clarification, the --lucene
>>>>> query option [1] and --sql query option [2] where I limit the query to
>>>> the
>>>>> product type that I ingested with, work fine.
>>>>> 
>>>>> Thanks,
>>>>> Sean
>>>>> 
>>>>> [1] query_tool --url ${FILEMGR_URL} --lucene -query "ProductType:
>>>>> CatalogFile"
>>>>> [2] query tool --url ${FILEMGR_URL} --sql -query "SELECT * FROM
>>>>> CatalogFile"
>>>>> 
>>>>> On 2/20/12 11:28 PM, "Mattmann, Chris A (388J)"
>>>>> <ch...@jpl.nasa.gov> wrote:
>>>>> 
>>>>>> Hey Sean,
>>>>>> 
>>>>>> Interesting. Can you try with 0.3 and see if it gives you a different
>>>>>> behavior? If it's a regression I'm happy to file an issue
>>>>>> and/or create a unit test for it.
>>>>>> 
>>>>>> Cheers,
>>>>>> Chris
>>>>>> 
>>>>>> On Feb 20, 2012, at 6:30 PM, Hardman, Sean H (388J) wrote:
>>>>>> 
>>>>>>> I first noticed this behavior in release 0.3 and just reaffirmed it
>> in
>>>>>>> a latest and greatest build of 0.4-SNAPSHOT. To the best of my
>>>>>>> knowledge, this was not the case in previous versions. When querying
>> a
>>>>>>> File Manager instance with a Lucene Catalog on the back end, the
>>>>>>> query_tool will throw an exception unless there is a product ingested
>>>>>>> for each product type listed in the policy (see the stack trace
>> below).
>>>>>>> 
>>>>>>> I assume I am not the first person to notice this behavior. Is this
>>>>>>> worthy of a JIRA issue?
>>>>>>> 
>>>>>>> Thanks,
>>>>>>> Sean
>>>>>>> 
>>>>>>> 
>>>>>>> bash-3.2$ ./query_tool --url ${FILEMGR_URL} --sql -query "SELECT *
>> FROM
>>>>>>> *"
>>>>>>> Feb 20, 2012 5:52:26 PM
>>>>>>> org.apache.oodt.cas.filemgr.catalog.LuceneCatalog paginateQuery
>>>>>>> WARNING: Query: [q=] for Product Type: [urn:pds:CatalogObject]
>> returned
>>>>>>> no results
>>>>>>> java.lang.NullPointerException
>>>>>>> at
>>>>>>> 
>>>> 
>> org.apache.oodt.cas.filemgr.system.XmlRpcFileManager.complexQuery(XmlRpcF
>>>>>>> ileManager.java:602)
>>>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>>>> at
>>>>>>> 
>>>> 
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java
>>>>>>> :39)
>>>>>>> at
>>>>>>> 
>>>> 
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorI
>>>>>>> mpl.java:25)
>>>>>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>>>>> at org.apache.xmlrpc.Invoker.execute(Invoker.java:130)
>>>>>>> at org.apache.xmlrpc.XmlRpcWorker.invokeHandler(XmlRpcWorker.java:84)
>>>>>>> at org.apache.xmlrpc.XmlRpcWorker.execute(XmlRpcWorker.java:146)
>>>>>>> at org.apache.xmlrpc.XmlRpcServer.execute(XmlRpcServer.java:139)
>>>>>>> at org.apache.xmlrpc.XmlRpcServer.execute(XmlRpcServer.java:125)
>>>>>>> at org.apache.xmlrpc.WebServer$Connection.run(WebServer.java:761)
>>>>>>> at org.apache.xmlrpc.WebServer$Runner.run(WebServer.java:642)
>>>>>>> at java.lang.Thread.run(Thread.java:680)
>>>>>>> org.apache.xmlrpc.XmlRpcException: java.lang.Exception:
>>>>>>> org.apache.oodt.cas.filemgr.structs.exceptions.CatalogException:
>> Failed
>>>>>>> to perform complex query : null
>>>>>>> at
>>>>>>> 
>>>> 
>> org.apache.xmlrpc.XmlRpcClientResponseProcessor.decodeException(XmlRpcCli
>>>>>>> entResponseProcessor.java:104)
>>>>>>> at
>>>>>>> 
>>>> 
>> org.apache.xmlrpc.XmlRpcClientResponseProcessor.decodeResponse(XmlRpcClie
>>>>>>> ntResponseProcessor.java:71)
>>>>>>> at
>>>>>>> 
>>>> org.apache.xmlrpc.XmlRpcClientWorker.execute(XmlRpcClientWorker.java:73)
>>>>>>> at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:194)
>>>>>>> at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:185)
>>>>>>> at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:178)
>>>>>>> at
>>>>>>> 
>>>> 
>> org.apache.oodt.cas.filemgr.system.XmlRpcFileManagerClient.complexQuery(X
>>>>>>> mlRpcFileManagerClient.java:974)
>>>>>>> at
>>>>>>> 
>>>> 
>> org.apache.oodt.cas.filemgr.tools.QueryTool.performSqlQuery(QueryTool.jav
>>>>>>> a:252)
>>>>>>> at
>> org.apache.oodt.cas.filemgr.tools.QueryTool.main(QueryTool.java:242)
>>>>>>> Exception in thread "main"
>>>>>>> org.apache.oodt.cas.filemgr.structs.exceptions.CatalogException:
>>>>>>> java.lang.Exception:
>>>>>>> org.apache.oodt.cas.filemgr.structs.exceptions.CatalogException:
>> Failed
>>>>>>> to perform complex query : null
>>>>>>> at
>>>>>>> 
>>>> 
>> org.apache.oodt.cas.filemgr.system.XmlRpcFileManagerClient.complexQuery(X
>>>>>>> mlRpcFileManagerClient.java:980)
>>>>>>> at
>>>>>>> 
>>>> 
>> org.apache.oodt.cas.filemgr.tools.QueryTool.performSqlQuery(QueryTool.jav
>>>>>>> a:252)
>>>>>>> at
>> org.apache.oodt.cas.filemgr.tools.QueryTool.main(QueryTool.java:242)
>>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>>> Chris Mattmann, Ph.D.
>>>>>> Senior Computer Scientist
>>>>>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
>>>>>> Office: 171-266B, Mailstop: 171-246
>>>>>> Email: chris.a.mattmann@nasa.gov
>>>>>> WWW:   http://sunset.usc.edu/~mattmann/
>>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>>> Adjunct Assistant Professor, Computer Science Department
>>>>>> University of Southern California, Los Angeles, CA 90089 USA
>>>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>>>> 
>>>>> 
>>>> 
>>>> 
>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>> Chris Mattmann, Ph.D.
>>>> Senior Computer Scientist
>>>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
>>>> Office: 171-266B, Mailstop: 171-246
>>>> Email: chris.a.mattmann@nasa.gov
>>>> WWW:   http://sunset.usc.edu/~mattmann/
>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>> Adjunct Assistant Professor, Computer Science Department
>>>> University of Southern California, Los Angeles, CA 90089 USA
>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>> 
>>>> 
>>> 
>>> 
>>> --
>>> -Sheryl
>> 
>> 
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> Chris Mattmann, Ph.D.
>> Senior Computer Scientist
>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
>> Office: 171-266B, Mailstop: 171-246
>> Email: chris.a.mattmann@nasa.gov
>> WWW:   http://sunset.usc.edu/~mattmann/
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> Adjunct Assistant Professor, Computer Science Department
>> University of Southern California, Los Angeles, CA 90089 USA
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> 
>> 
> 
> 
> --
> -Sheryl


++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW:   http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++


Re: Issue with query_tool when all product types are not populated

Posted by Sheryl John <sh...@gmail.com>.
I've added an issue for this :
https://issues.apache.org/jira/browse/OODT-384

Thanks,

On Wed, Feb 22, 2012 at 9:38 PM, Mattmann, Chris A (388J) <
chris.a.mattmann@jpl.nasa.gov> wrote:

> Thanks for the case Sheryl. Would you mind filing a JIRA issue for 0.5 to
> investigate this?
>
> Cheers,
> Chris
>
> On Feb 22, 2012, at 3:49 PM, Sheryl John wrote:
>
> > Hi,
> >
> > I've experienced the same today while working with 0.4-snapshot (not
> latest
> > build ) and also the query does not seem to accept '*' for the elements.
> > For the following use case:
> >
> > ./filemgr-client --url http://localhost:9000 -op -sql -query "SELECT *
> FROM
> > CernerLocations"
> >
> > The stack trace:
> >
> > Feb 22, 2012 2:36:52 PM
> > org.apache.oodt.cas.filemgr.system.XmlRpcFileManager complexQuery
> > INFO: Query returned 2 results
> > org.apache.xmlrpc.XmlRpcException: org.apache.xmlrpc.XmlRpcException:
> null
> > values not supported by XML-RPC
> > at
> >
> org.apache.xmlrpc.XmlRpcClientResponseProcessor.decodeException(XmlRpcClientResponseProcessor.java:104)
> > at
> >
> org.apache.xmlrpc.XmlRpcClientResponseProcessor.decodeResponse(XmlRpcClientResponseProcessor.java:71)
> > at
> org.apache.xmlrpc.XmlRpcClientWorker.execute(XmlRpcClientWorker.java:73)
> > at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:194)
> > at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:185)
> > at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:178)
> > at
> >
> org.apache.oodt.cas.filemgr.system.XmlRpcFileManagerClient.complexQuery(XmlRpcFileManagerClient.java:974)
> > at
> >
> org.apache.oodt.cas.filemgr.cli.action.AbstractQueryCliAction.execute(AbstractQueryCliAction.java:75)
> > at
> org.apache.oodt.cas.cli.CmdLineUtility.execute(CmdLineUtility.java:296)
> > at org.apache.oodt.cas.cli.CmdLineUtility.run(CmdLineUtility.java:179)
> > at
> >
> org.apache.oodt.cas.filemgr.system.XmlRpcFileManagerClient.main(XmlRpcFileManagerClient.java:1307)
> > ERROR: Failed to perform sql query : sortBy 'null', outputFormat 'null',
> > and delimiter '
> > ', filterAlgor 'null', startDateTimeMetKey 'null', endDateTimeMetKey
> > 'null', priorityMetKey 'null', null' : org.apache.xmlrpc.XmlRpcException:
> > null values not supported by XML-RPC
> >
> >
> > But if add the elements' names in the query I get the desired query
> results.
> >
> > ./filemgr-client --url http://palmer:9000 -op -sql -query "SELECT
> > CAS.ProductName,PID FROM CernerLocations"
> >
> > Feb 22, 2012 2:45:22 PM
> > org.apache.oodt.cas.filemgr.system.XmlRpcFileManager complexQuery
> > INFO: Query returned 2 results
> > blah_xx.csv,xxxx
> > blah_yy.csv,yyyy
> >
> >
> >
> >
> > On Tue, Feb 21, 2012 at 1:38 PM, Mattmann, Chris A (388J) <
> > chris.a.mattmann@jpl.nasa.gov> wrote:
> >
> >> Hey Sean,
> >>
> >> Thanks for the FYI. OK, so it's not a regression, but it sounds worthy
> of
> >> a JIRA
> >> issue. I'd say go for it and let's investigate the fix, even if it means
> >> porting it
> >> out of wengine.
> >>
> >> Cheers,
> >> Chris
> >>
> >> On Feb 21, 2012, at 10:23 AM, Hardman, Sean H (388J) wrote:
> >>
> >>> Hey Chris,
> >>>
> >>> Yes, the identical behavior can be seen 0.3, I am just slow to complain
> >>> about it. I haven't tried 0.2, but this query does work successfully in
> >>> the wengine-branch version of the FM. For clarification, the --lucene
> >>> query option [1] and --sql query option [2] where I limit the query to
> >> the
> >>> product type that I ingested with, work fine.
> >>>
> >>> Thanks,
> >>> Sean
> >>>
> >>> [1] query_tool --url ${FILEMGR_URL} --lucene -query "ProductType:
> >>> CatalogFile"
> >>> [2] query tool --url ${FILEMGR_URL} --sql -query "SELECT * FROM
> >>> CatalogFile"
> >>>
> >>> On 2/20/12 11:28 PM, "Mattmann, Chris A (388J)"
> >>> <ch...@jpl.nasa.gov> wrote:
> >>>
> >>>> Hey Sean,
> >>>>
> >>>> Interesting. Can you try with 0.3 and see if it gives you a different
> >>>> behavior? If it's a regression I'm happy to file an issue
> >>>> and/or create a unit test for it.
> >>>>
> >>>> Cheers,
> >>>> Chris
> >>>>
> >>>> On Feb 20, 2012, at 6:30 PM, Hardman, Sean H (388J) wrote:
> >>>>
> >>>>> I first noticed this behavior in release 0.3 and just reaffirmed it
> in
> >>>>> a latest and greatest build of 0.4-SNAPSHOT. To the best of my
> >>>>> knowledge, this was not the case in previous versions. When querying
> a
> >>>>> File Manager instance with a Lucene Catalog on the back end, the
> >>>>> query_tool will throw an exception unless there is a product ingested
> >>>>> for each product type listed in the policy (see the stack trace
> below).
> >>>>>
> >>>>> I assume I am not the first person to notice this behavior. Is this
> >>>>> worthy of a JIRA issue?
> >>>>>
> >>>>> Thanks,
> >>>>> Sean
> >>>>>
> >>>>>
> >>>>> bash-3.2$ ./query_tool --url ${FILEMGR_URL} --sql -query "SELECT *
> FROM
> >>>>> *"
> >>>>> Feb 20, 2012 5:52:26 PM
> >>>>> org.apache.oodt.cas.filemgr.catalog.LuceneCatalog paginateQuery
> >>>>> WARNING: Query: [q=] for Product Type: [urn:pds:CatalogObject]
> returned
> >>>>> no results
> >>>>> java.lang.NullPointerException
> >>>>> at
> >>>>>
> >>
> org.apache.oodt.cas.filemgr.system.XmlRpcFileManager.complexQuery(XmlRpcF
> >>>>> ileManager.java:602)
> >>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >>>>> at
> >>>>>
> >>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java
> >>>>> :39)
> >>>>> at
> >>>>>
> >>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorI
> >>>>> mpl.java:25)
> >>>>> at java.lang.reflect.Method.invoke(Method.java:597)
> >>>>> at org.apache.xmlrpc.Invoker.execute(Invoker.java:130)
> >>>>> at org.apache.xmlrpc.XmlRpcWorker.invokeHandler(XmlRpcWorker.java:84)
> >>>>> at org.apache.xmlrpc.XmlRpcWorker.execute(XmlRpcWorker.java:146)
> >>>>> at org.apache.xmlrpc.XmlRpcServer.execute(XmlRpcServer.java:139)
> >>>>> at org.apache.xmlrpc.XmlRpcServer.execute(XmlRpcServer.java:125)
> >>>>> at org.apache.xmlrpc.WebServer$Connection.run(WebServer.java:761)
> >>>>> at org.apache.xmlrpc.WebServer$Runner.run(WebServer.java:642)
> >>>>> at java.lang.Thread.run(Thread.java:680)
> >>>>> org.apache.xmlrpc.XmlRpcException: java.lang.Exception:
> >>>>> org.apache.oodt.cas.filemgr.structs.exceptions.CatalogException:
> Failed
> >>>>> to perform complex query : null
> >>>>> at
> >>>>>
> >>
> org.apache.xmlrpc.XmlRpcClientResponseProcessor.decodeException(XmlRpcCli
> >>>>> entResponseProcessor.java:104)
> >>>>> at
> >>>>>
> >>
> org.apache.xmlrpc.XmlRpcClientResponseProcessor.decodeResponse(XmlRpcClie
> >>>>> ntResponseProcessor.java:71)
> >>>>> at
> >>>>>
> >> org.apache.xmlrpc.XmlRpcClientWorker.execute(XmlRpcClientWorker.java:73)
> >>>>> at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:194)
> >>>>> at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:185)
> >>>>> at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:178)
> >>>>> at
> >>>>>
> >>
> org.apache.oodt.cas.filemgr.system.XmlRpcFileManagerClient.complexQuery(X
> >>>>> mlRpcFileManagerClient.java:974)
> >>>>> at
> >>>>>
> >>
> org.apache.oodt.cas.filemgr.tools.QueryTool.performSqlQuery(QueryTool.jav
> >>>>> a:252)
> >>>>> at
> org.apache.oodt.cas.filemgr.tools.QueryTool.main(QueryTool.java:242)
> >>>>> Exception in thread "main"
> >>>>> org.apache.oodt.cas.filemgr.structs.exceptions.CatalogException:
> >>>>> java.lang.Exception:
> >>>>> org.apache.oodt.cas.filemgr.structs.exceptions.CatalogException:
> Failed
> >>>>> to perform complex query : null
> >>>>> at
> >>>>>
> >>
> org.apache.oodt.cas.filemgr.system.XmlRpcFileManagerClient.complexQuery(X
> >>>>> mlRpcFileManagerClient.java:980)
> >>>>> at
> >>>>>
> >>
> org.apache.oodt.cas.filemgr.tools.QueryTool.performSqlQuery(QueryTool.jav
> >>>>> a:252)
> >>>>> at
> org.apache.oodt.cas.filemgr.tools.QueryTool.main(QueryTool.java:242)
> >>>>>
> >>>>
> >>>>
> >>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >>>> Chris Mattmann, Ph.D.
> >>>> Senior Computer Scientist
> >>>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> >>>> Office: 171-266B, Mailstop: 171-246
> >>>> Email: chris.a.mattmann@nasa.gov
> >>>> WWW:   http://sunset.usc.edu/~mattmann/
> >>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >>>> Adjunct Assistant Professor, Computer Science Department
> >>>> University of Southern California, Los Angeles, CA 90089 USA
> >>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >>>>
> >>>
> >>
> >>
> >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >> Chris Mattmann, Ph.D.
> >> Senior Computer Scientist
> >> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> >> Office: 171-266B, Mailstop: 171-246
> >> Email: chris.a.mattmann@nasa.gov
> >> WWW:   http://sunset.usc.edu/~mattmann/
> >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >> Adjunct Assistant Professor, Computer Science Department
> >> University of Southern California, Los Angeles, CA 90089 USA
> >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >>
> >>
> >
> >
> > --
> > -Sheryl
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: chris.a.mattmann@nasa.gov
> WWW:   http://sunset.usc.edu/~mattmann/
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>


-- 
-Sheryl

Re: Issue with query_tool when all product types are not populated

Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Thanks for the case Sheryl. Would you mind filing a JIRA issue for 0.5 to investigate this?

Cheers,
Chris

On Feb 22, 2012, at 3:49 PM, Sheryl John wrote:

> Hi,
> 
> I've experienced the same today while working with 0.4-snapshot (not latest
> build ) and also the query does not seem to accept '*' for the elements.
> For the following use case:
> 
> ./filemgr-client --url http://localhost:9000 -op -sql -query "SELECT * FROM
> CernerLocations"
> 
> The stack trace:
> 
> Feb 22, 2012 2:36:52 PM
> org.apache.oodt.cas.filemgr.system.XmlRpcFileManager complexQuery
> INFO: Query returned 2 results
> org.apache.xmlrpc.XmlRpcException: org.apache.xmlrpc.XmlRpcException: null
> values not supported by XML-RPC
> at
> org.apache.xmlrpc.XmlRpcClientResponseProcessor.decodeException(XmlRpcClientResponseProcessor.java:104)
> at
> org.apache.xmlrpc.XmlRpcClientResponseProcessor.decodeResponse(XmlRpcClientResponseProcessor.java:71)
> at org.apache.xmlrpc.XmlRpcClientWorker.execute(XmlRpcClientWorker.java:73)
> at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:194)
> at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:185)
> at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:178)
> at
> org.apache.oodt.cas.filemgr.system.XmlRpcFileManagerClient.complexQuery(XmlRpcFileManagerClient.java:974)
> at
> org.apache.oodt.cas.filemgr.cli.action.AbstractQueryCliAction.execute(AbstractQueryCliAction.java:75)
> at org.apache.oodt.cas.cli.CmdLineUtility.execute(CmdLineUtility.java:296)
> at org.apache.oodt.cas.cli.CmdLineUtility.run(CmdLineUtility.java:179)
> at
> org.apache.oodt.cas.filemgr.system.XmlRpcFileManagerClient.main(XmlRpcFileManagerClient.java:1307)
> ERROR: Failed to perform sql query : sortBy 'null', outputFormat 'null',
> and delimiter '
> ', filterAlgor 'null', startDateTimeMetKey 'null', endDateTimeMetKey
> 'null', priorityMetKey 'null', null' : org.apache.xmlrpc.XmlRpcException:
> null values not supported by XML-RPC
> 
> 
> But if add the elements' names in the query I get the desired query results.
> 
> ./filemgr-client --url http://palmer:9000 -op -sql -query "SELECT
> CAS.ProductName,PID FROM CernerLocations"
> 
> Feb 22, 2012 2:45:22 PM
> org.apache.oodt.cas.filemgr.system.XmlRpcFileManager complexQuery
> INFO: Query returned 2 results
> blah_xx.csv,xxxx
> blah_yy.csv,yyyy
> 
> 
> 
> 
> On Tue, Feb 21, 2012 at 1:38 PM, Mattmann, Chris A (388J) <
> chris.a.mattmann@jpl.nasa.gov> wrote:
> 
>> Hey Sean,
>> 
>> Thanks for the FYI. OK, so it's not a regression, but it sounds worthy of
>> a JIRA
>> issue. I'd say go for it and let's investigate the fix, even if it means
>> porting it
>> out of wengine.
>> 
>> Cheers,
>> Chris
>> 
>> On Feb 21, 2012, at 10:23 AM, Hardman, Sean H (388J) wrote:
>> 
>>> Hey Chris,
>>> 
>>> Yes, the identical behavior can be seen 0.3, I am just slow to complain
>>> about it. I haven't tried 0.2, but this query does work successfully in
>>> the wengine-branch version of the FM. For clarification, the --lucene
>>> query option [1] and --sql query option [2] where I limit the query to
>> the
>>> product type that I ingested with, work fine.
>>> 
>>> Thanks,
>>> Sean
>>> 
>>> [1] query_tool --url ${FILEMGR_URL} --lucene -query "ProductType:
>>> CatalogFile"
>>> [2] query tool --url ${FILEMGR_URL} --sql -query "SELECT * FROM
>>> CatalogFile"
>>> 
>>> On 2/20/12 11:28 PM, "Mattmann, Chris A (388J)"
>>> <ch...@jpl.nasa.gov> wrote:
>>> 
>>>> Hey Sean,
>>>> 
>>>> Interesting. Can you try with 0.3 and see if it gives you a different
>>>> behavior? If it's a regression I'm happy to file an issue
>>>> and/or create a unit test for it.
>>>> 
>>>> Cheers,
>>>> Chris
>>>> 
>>>> On Feb 20, 2012, at 6:30 PM, Hardman, Sean H (388J) wrote:
>>>> 
>>>>> I first noticed this behavior in release 0.3 and just reaffirmed it in
>>>>> a latest and greatest build of 0.4-SNAPSHOT. To the best of my
>>>>> knowledge, this was not the case in previous versions. When querying a
>>>>> File Manager instance with a Lucene Catalog on the back end, the
>>>>> query_tool will throw an exception unless there is a product ingested
>>>>> for each product type listed in the policy (see the stack trace below).
>>>>> 
>>>>> I assume I am not the first person to notice this behavior. Is this
>>>>> worthy of a JIRA issue?
>>>>> 
>>>>> Thanks,
>>>>> Sean
>>>>> 
>>>>> 
>>>>> bash-3.2$ ./query_tool --url ${FILEMGR_URL} --sql -query "SELECT * FROM
>>>>> *"
>>>>> Feb 20, 2012 5:52:26 PM
>>>>> org.apache.oodt.cas.filemgr.catalog.LuceneCatalog paginateQuery
>>>>> WARNING: Query: [q=] for Product Type: [urn:pds:CatalogObject] returned
>>>>> no results
>>>>> java.lang.NullPointerException
>>>>> at
>>>>> 
>> org.apache.oodt.cas.filemgr.system.XmlRpcFileManager.complexQuery(XmlRpcF
>>>>> ileManager.java:602)
>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>>> at
>>>>> 
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java
>>>>> :39)
>>>>> at
>>>>> 
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorI
>>>>> mpl.java:25)
>>>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>>> at org.apache.xmlrpc.Invoker.execute(Invoker.java:130)
>>>>> at org.apache.xmlrpc.XmlRpcWorker.invokeHandler(XmlRpcWorker.java:84)
>>>>> at org.apache.xmlrpc.XmlRpcWorker.execute(XmlRpcWorker.java:146)
>>>>> at org.apache.xmlrpc.XmlRpcServer.execute(XmlRpcServer.java:139)
>>>>> at org.apache.xmlrpc.XmlRpcServer.execute(XmlRpcServer.java:125)
>>>>> at org.apache.xmlrpc.WebServer$Connection.run(WebServer.java:761)
>>>>> at org.apache.xmlrpc.WebServer$Runner.run(WebServer.java:642)
>>>>> at java.lang.Thread.run(Thread.java:680)
>>>>> org.apache.xmlrpc.XmlRpcException: java.lang.Exception:
>>>>> org.apache.oodt.cas.filemgr.structs.exceptions.CatalogException: Failed
>>>>> to perform complex query : null
>>>>> at
>>>>> 
>> org.apache.xmlrpc.XmlRpcClientResponseProcessor.decodeException(XmlRpcCli
>>>>> entResponseProcessor.java:104)
>>>>> at
>>>>> 
>> org.apache.xmlrpc.XmlRpcClientResponseProcessor.decodeResponse(XmlRpcClie
>>>>> ntResponseProcessor.java:71)
>>>>> at
>>>>> 
>> org.apache.xmlrpc.XmlRpcClientWorker.execute(XmlRpcClientWorker.java:73)
>>>>> at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:194)
>>>>> at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:185)
>>>>> at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:178)
>>>>> at
>>>>> 
>> org.apache.oodt.cas.filemgr.system.XmlRpcFileManagerClient.complexQuery(X
>>>>> mlRpcFileManagerClient.java:974)
>>>>> at
>>>>> 
>> org.apache.oodt.cas.filemgr.tools.QueryTool.performSqlQuery(QueryTool.jav
>>>>> a:252)
>>>>> at org.apache.oodt.cas.filemgr.tools.QueryTool.main(QueryTool.java:242)
>>>>> Exception in thread "main"
>>>>> org.apache.oodt.cas.filemgr.structs.exceptions.CatalogException:
>>>>> java.lang.Exception:
>>>>> org.apache.oodt.cas.filemgr.structs.exceptions.CatalogException: Failed
>>>>> to perform complex query : null
>>>>> at
>>>>> 
>> org.apache.oodt.cas.filemgr.system.XmlRpcFileManagerClient.complexQuery(X
>>>>> mlRpcFileManagerClient.java:980)
>>>>> at
>>>>> 
>> org.apache.oodt.cas.filemgr.tools.QueryTool.performSqlQuery(QueryTool.jav
>>>>> a:252)
>>>>> at org.apache.oodt.cas.filemgr.tools.QueryTool.main(QueryTool.java:242)
>>>>> 
>>>> 
>>>> 
>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>> Chris Mattmann, Ph.D.
>>>> Senior Computer Scientist
>>>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
>>>> Office: 171-266B, Mailstop: 171-246
>>>> Email: chris.a.mattmann@nasa.gov
>>>> WWW:   http://sunset.usc.edu/~mattmann/
>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>> Adjunct Assistant Professor, Computer Science Department
>>>> University of Southern California, Los Angeles, CA 90089 USA
>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>> 
>>> 
>> 
>> 
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> Chris Mattmann, Ph.D.
>> Senior Computer Scientist
>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
>> Office: 171-266B, Mailstop: 171-246
>> Email: chris.a.mattmann@nasa.gov
>> WWW:   http://sunset.usc.edu/~mattmann/
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> Adjunct Assistant Professor, Computer Science Department
>> University of Southern California, Los Angeles, CA 90089 USA
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> 
>> 
> 
> 
> -- 
> -Sheryl


++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW:   http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++


Re: Issue with query_tool when all product types are not populated

Posted by Sheryl John <sh...@gmail.com>.
Hi,

I've experienced the same today while working with 0.4-snapshot (not latest
build ) and also the query does not seem to accept '*' for the elements.
For the following use case:

./filemgr-client --url http://localhost:9000 -op -sql -query "SELECT * FROM
CernerLocations"

The stack trace:

Feb 22, 2012 2:36:52 PM
org.apache.oodt.cas.filemgr.system.XmlRpcFileManager complexQuery
INFO: Query returned 2 results
org.apache.xmlrpc.XmlRpcException: org.apache.xmlrpc.XmlRpcException: null
values not supported by XML-RPC
at
org.apache.xmlrpc.XmlRpcClientResponseProcessor.decodeException(XmlRpcClientResponseProcessor.java:104)
at
org.apache.xmlrpc.XmlRpcClientResponseProcessor.decodeResponse(XmlRpcClientResponseProcessor.java:71)
at org.apache.xmlrpc.XmlRpcClientWorker.execute(XmlRpcClientWorker.java:73)
at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:194)
at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:185)
at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:178)
at
org.apache.oodt.cas.filemgr.system.XmlRpcFileManagerClient.complexQuery(XmlRpcFileManagerClient.java:974)
at
org.apache.oodt.cas.filemgr.cli.action.AbstractQueryCliAction.execute(AbstractQueryCliAction.java:75)
at org.apache.oodt.cas.cli.CmdLineUtility.execute(CmdLineUtility.java:296)
at org.apache.oodt.cas.cli.CmdLineUtility.run(CmdLineUtility.java:179)
at
org.apache.oodt.cas.filemgr.system.XmlRpcFileManagerClient.main(XmlRpcFileManagerClient.java:1307)
ERROR: Failed to perform sql query : sortBy 'null', outputFormat 'null',
and delimiter '
', filterAlgor 'null', startDateTimeMetKey 'null', endDateTimeMetKey
'null', priorityMetKey 'null', null' : org.apache.xmlrpc.XmlRpcException:
null values not supported by XML-RPC


But if add the elements' names in the query I get the desired query results.

./filemgr-client --url http://palmer:9000 -op -sql -query "SELECT
CAS.ProductName,PID FROM CernerLocations"

Feb 22, 2012 2:45:22 PM
org.apache.oodt.cas.filemgr.system.XmlRpcFileManager complexQuery
INFO: Query returned 2 results
blah_xx.csv,xxxx
blah_yy.csv,yyyy




On Tue, Feb 21, 2012 at 1:38 PM, Mattmann, Chris A (388J) <
chris.a.mattmann@jpl.nasa.gov> wrote:

> Hey Sean,
>
> Thanks for the FYI. OK, so it's not a regression, but it sounds worthy of
> a JIRA
> issue. I'd say go for it and let's investigate the fix, even if it means
> porting it
> out of wengine.
>
> Cheers,
> Chris
>
> On Feb 21, 2012, at 10:23 AM, Hardman, Sean H (388J) wrote:
>
> > Hey Chris,
> >
> > Yes, the identical behavior can be seen 0.3, I am just slow to complain
> > about it. I haven't tried 0.2, but this query does work successfully in
> > the wengine-branch version of the FM. For clarification, the --lucene
> > query option [1] and --sql query option [2] where I limit the query to
> the
> > product type that I ingested with, work fine.
> >
> > Thanks,
> > Sean
> >
> > [1] query_tool --url ${FILEMGR_URL} --lucene -query "ProductType:
> > CatalogFile"
> > [2] query tool --url ${FILEMGR_URL} --sql -query "SELECT * FROM
> > CatalogFile"
> >
> > On 2/20/12 11:28 PM, "Mattmann, Chris A (388J)"
> > <ch...@jpl.nasa.gov> wrote:
> >
> >> Hey Sean,
> >>
> >> Interesting. Can you try with 0.3 and see if it gives you a different
> >> behavior? If it's a regression I'm happy to file an issue
> >> and/or create a unit test for it.
> >>
> >> Cheers,
> >> Chris
> >>
> >> On Feb 20, 2012, at 6:30 PM, Hardman, Sean H (388J) wrote:
> >>
> >>> I first noticed this behavior in release 0.3 and just reaffirmed it in
> >>> a latest and greatest build of 0.4-SNAPSHOT. To the best of my
> >>> knowledge, this was not the case in previous versions. When querying a
> >>> File Manager instance with a Lucene Catalog on the back end, the
> >>> query_tool will throw an exception unless there is a product ingested
> >>> for each product type listed in the policy (see the stack trace below).
> >>>
> >>> I assume I am not the first person to notice this behavior. Is this
> >>> worthy of a JIRA issue?
> >>>
> >>> Thanks,
> >>> Sean
> >>>
> >>>
> >>> bash-3.2$ ./query_tool --url ${FILEMGR_URL} --sql -query "SELECT * FROM
> >>> *"
> >>> Feb 20, 2012 5:52:26 PM
> >>> org.apache.oodt.cas.filemgr.catalog.LuceneCatalog paginateQuery
> >>> WARNING: Query: [q=] for Product Type: [urn:pds:CatalogObject] returned
> >>> no results
> >>> java.lang.NullPointerException
> >>> at
> >>>
> org.apache.oodt.cas.filemgr.system.XmlRpcFileManager.complexQuery(XmlRpcF
> >>> ileManager.java:602)
> >>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >>> at
> >>>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java
> >>> :39)
> >>> at
> >>>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorI
> >>> mpl.java:25)
> >>> at java.lang.reflect.Method.invoke(Method.java:597)
> >>> at org.apache.xmlrpc.Invoker.execute(Invoker.java:130)
> >>> at org.apache.xmlrpc.XmlRpcWorker.invokeHandler(XmlRpcWorker.java:84)
> >>> at org.apache.xmlrpc.XmlRpcWorker.execute(XmlRpcWorker.java:146)
> >>> at org.apache.xmlrpc.XmlRpcServer.execute(XmlRpcServer.java:139)
> >>> at org.apache.xmlrpc.XmlRpcServer.execute(XmlRpcServer.java:125)
> >>> at org.apache.xmlrpc.WebServer$Connection.run(WebServer.java:761)
> >>> at org.apache.xmlrpc.WebServer$Runner.run(WebServer.java:642)
> >>> at java.lang.Thread.run(Thread.java:680)
> >>> org.apache.xmlrpc.XmlRpcException: java.lang.Exception:
> >>> org.apache.oodt.cas.filemgr.structs.exceptions.CatalogException: Failed
> >>> to perform complex query : null
> >>> at
> >>>
> org.apache.xmlrpc.XmlRpcClientResponseProcessor.decodeException(XmlRpcCli
> >>> entResponseProcessor.java:104)
> >>> at
> >>>
> org.apache.xmlrpc.XmlRpcClientResponseProcessor.decodeResponse(XmlRpcClie
> >>> ntResponseProcessor.java:71)
> >>> at
> >>>
> org.apache.xmlrpc.XmlRpcClientWorker.execute(XmlRpcClientWorker.java:73)
> >>> at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:194)
> >>> at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:185)
> >>> at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:178)
> >>> at
> >>>
> org.apache.oodt.cas.filemgr.system.XmlRpcFileManagerClient.complexQuery(X
> >>> mlRpcFileManagerClient.java:974)
> >>> at
> >>>
> org.apache.oodt.cas.filemgr.tools.QueryTool.performSqlQuery(QueryTool.jav
> >>> a:252)
> >>> at org.apache.oodt.cas.filemgr.tools.QueryTool.main(QueryTool.java:242)
> >>> Exception in thread "main"
> >>> org.apache.oodt.cas.filemgr.structs.exceptions.CatalogException:
> >>> java.lang.Exception:
> >>> org.apache.oodt.cas.filemgr.structs.exceptions.CatalogException: Failed
> >>> to perform complex query : null
> >>> at
> >>>
> org.apache.oodt.cas.filemgr.system.XmlRpcFileManagerClient.complexQuery(X
> >>> mlRpcFileManagerClient.java:980)
> >>> at
> >>>
> org.apache.oodt.cas.filemgr.tools.QueryTool.performSqlQuery(QueryTool.jav
> >>> a:252)
> >>> at org.apache.oodt.cas.filemgr.tools.QueryTool.main(QueryTool.java:242)
> >>>
> >>
> >>
> >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >> Chris Mattmann, Ph.D.
> >> Senior Computer Scientist
> >> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> >> Office: 171-266B, Mailstop: 171-246
> >> Email: chris.a.mattmann@nasa.gov
> >> WWW:   http://sunset.usc.edu/~mattmann/
> >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >> Adjunct Assistant Professor, Computer Science Department
> >> University of Southern California, Los Angeles, CA 90089 USA
> >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >>
> >
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: chris.a.mattmann@nasa.gov
> WWW:   http://sunset.usc.edu/~mattmann/
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>


-- 
-Sheryl

Re: Issue with query_tool when all product types are not populated

Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hey Sean,

Thanks for the FYI. OK, so it's not a regression, but it sounds worthy of a JIRA
issue. I'd say go for it and let's investigate the fix, even if it means porting it
out of wengine. 

Cheers,
Chris

On Feb 21, 2012, at 10:23 AM, Hardman, Sean H (388J) wrote:

> Hey Chris,
> 
> Yes, the identical behavior can be seen 0.3, I am just slow to complain
> about it. I haven't tried 0.2, but this query does work successfully in
> the wengine-branch version of the FM. For clarification, the --lucene
> query option [1] and --sql query option [2] where I limit the query to the
> product type that I ingested with, work fine.
> 
> Thanks,
> Sean
> 
> [1] query_tool --url ${FILEMGR_URL} --lucene -query "ProductType:
> CatalogFile"
> [2] query tool --url ${FILEMGR_URL} --sql -query "SELECT * FROM
> CatalogFile"
> 
> On 2/20/12 11:28 PM, "Mattmann, Chris A (388J)"
> <ch...@jpl.nasa.gov> wrote:
> 
>> Hey Sean,
>> 
>> Interesting. Can you try with 0.3 and see if it gives you a different
>> behavior? If it's a regression I'm happy to file an issue
>> and/or create a unit test for it.
>> 
>> Cheers,
>> Chris
>> 
>> On Feb 20, 2012, at 6:30 PM, Hardman, Sean H (388J) wrote:
>> 
>>> I first noticed this behavior in release 0.3 and just reaffirmed it in
>>> a latest and greatest build of 0.4-SNAPSHOT. To the best of my
>>> knowledge, this was not the case in previous versions. When querying a
>>> File Manager instance with a Lucene Catalog on the back end, the
>>> query_tool will throw an exception unless there is a product ingested
>>> for each product type listed in the policy (see the stack trace below).
>>> 
>>> I assume I am not the first person to notice this behavior. Is this
>>> worthy of a JIRA issue?
>>> 
>>> Thanks,
>>> Sean
>>> 
>>> 
>>> bash-3.2$ ./query_tool --url ${FILEMGR_URL} --sql -query "SELECT * FROM
>>> *"
>>> Feb 20, 2012 5:52:26 PM
>>> org.apache.oodt.cas.filemgr.catalog.LuceneCatalog paginateQuery
>>> WARNING: Query: [q=] for Product Type: [urn:pds:CatalogObject] returned
>>> no results
>>> java.lang.NullPointerException
>>> at 
>>> org.apache.oodt.cas.filemgr.system.XmlRpcFileManager.complexQuery(XmlRpcF
>>> ileManager.java:602)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at 
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java
>>> :39)
>>> at 
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorI
>>> mpl.java:25)
>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>> at org.apache.xmlrpc.Invoker.execute(Invoker.java:130)
>>> at org.apache.xmlrpc.XmlRpcWorker.invokeHandler(XmlRpcWorker.java:84)
>>> at org.apache.xmlrpc.XmlRpcWorker.execute(XmlRpcWorker.java:146)
>>> at org.apache.xmlrpc.XmlRpcServer.execute(XmlRpcServer.java:139)
>>> at org.apache.xmlrpc.XmlRpcServer.execute(XmlRpcServer.java:125)
>>> at org.apache.xmlrpc.WebServer$Connection.run(WebServer.java:761)
>>> at org.apache.xmlrpc.WebServer$Runner.run(WebServer.java:642)
>>> at java.lang.Thread.run(Thread.java:680)
>>> org.apache.xmlrpc.XmlRpcException: java.lang.Exception:
>>> org.apache.oodt.cas.filemgr.structs.exceptions.CatalogException: Failed
>>> to perform complex query : null
>>> at 
>>> org.apache.xmlrpc.XmlRpcClientResponseProcessor.decodeException(XmlRpcCli
>>> entResponseProcessor.java:104)
>>> at 
>>> org.apache.xmlrpc.XmlRpcClientResponseProcessor.decodeResponse(XmlRpcClie
>>> ntResponseProcessor.java:71)
>>> at 
>>> org.apache.xmlrpc.XmlRpcClientWorker.execute(XmlRpcClientWorker.java:73)
>>> at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:194)
>>> at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:185)
>>> at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:178)
>>> at 
>>> org.apache.oodt.cas.filemgr.system.XmlRpcFileManagerClient.complexQuery(X
>>> mlRpcFileManagerClient.java:974)
>>> at 
>>> org.apache.oodt.cas.filemgr.tools.QueryTool.performSqlQuery(QueryTool.jav
>>> a:252)
>>> at org.apache.oodt.cas.filemgr.tools.QueryTool.main(QueryTool.java:242)
>>> Exception in thread "main"
>>> org.apache.oodt.cas.filemgr.structs.exceptions.CatalogException:
>>> java.lang.Exception:
>>> org.apache.oodt.cas.filemgr.structs.exceptions.CatalogException: Failed
>>> to perform complex query : null
>>> at 
>>> org.apache.oodt.cas.filemgr.system.XmlRpcFileManagerClient.complexQuery(X
>>> mlRpcFileManagerClient.java:980)
>>> at 
>>> org.apache.oodt.cas.filemgr.tools.QueryTool.performSqlQuery(QueryTool.jav
>>> a:252)
>>> at org.apache.oodt.cas.filemgr.tools.QueryTool.main(QueryTool.java:242)
>>> 
>> 
>> 
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> Chris Mattmann, Ph.D.
>> Senior Computer Scientist
>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
>> Office: 171-266B, Mailstop: 171-246
>> Email: chris.a.mattmann@nasa.gov
>> WWW:   http://sunset.usc.edu/~mattmann/
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> Adjunct Assistant Professor, Computer Science Department
>> University of Southern California, Los Angeles, CA 90089 USA
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> 
> 


++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW:   http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++


Re: Issue with query_tool when all product types are not populated

Posted by "Hardman, Sean H (388J)" <se...@jpl.nasa.gov>.
Hey Chris,

Yes, the identical behavior can be seen 0.3, I am just slow to complain
about it. I haven't tried 0.2, but this query does work successfully in
the wengine-branch version of the FM. For clarification, the --lucene
query option [1] and --sql query option [2] where I limit the query to the
product type that I ingested with, work fine.

Thanks,
Sean

[1] query_tool --url ${FILEMGR_URL} --lucene -query "ProductType:
CatalogFile"
[2] query tool --url ${FILEMGR_URL} --sql -query "SELECT * FROM
CatalogFile"

On 2/20/12 11:28 PM, "Mattmann, Chris A (388J)"
<ch...@jpl.nasa.gov> wrote:

>Hey Sean,
>
>Interesting. Can you try with 0.3 and see if it gives you a different
>behavior? If it's a regression I'm happy to file an issue
>and/or create a unit test for it.
>
>Cheers,
>Chris
>
>On Feb 20, 2012, at 6:30 PM, Hardman, Sean H (388J) wrote:
>
>> I first noticed this behavior in release 0.3 and just reaffirmed it in
>>a latest and greatest build of 0.4-SNAPSHOT. To the best of my
>>knowledge, this was not the case in previous versions. When querying a
>>File Manager instance with a Lucene Catalog on the back end, the
>>query_tool will throw an exception unless there is a product ingested
>>for each product type listed in the policy (see the stack trace below).
>> 
>> I assume I am not the first person to notice this behavior. Is this
>>worthy of a JIRA issue?
>> 
>> Thanks,
>> Sean
>> 
>> 
>> bash-3.2$ ./query_tool --url ${FILEMGR_URL} --sql -query "SELECT * FROM
>>*"
>> Feb 20, 2012 5:52:26 PM
>>org.apache.oodt.cas.filemgr.catalog.LuceneCatalog paginateQuery
>> WARNING: Query: [q=] for Product Type: [urn:pds:CatalogObject] returned
>>no results
>> java.lang.NullPointerException
>> at 
>>org.apache.oodt.cas.filemgr.system.XmlRpcFileManager.complexQuery(XmlRpcF
>>ileManager.java:602)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at 
>>sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java
>>:39)
>> at 
>>sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorI
>>mpl.java:25)
>> at java.lang.reflect.Method.invoke(Method.java:597)
>> at org.apache.xmlrpc.Invoker.execute(Invoker.java:130)
>> at org.apache.xmlrpc.XmlRpcWorker.invokeHandler(XmlRpcWorker.java:84)
>> at org.apache.xmlrpc.XmlRpcWorker.execute(XmlRpcWorker.java:146)
>> at org.apache.xmlrpc.XmlRpcServer.execute(XmlRpcServer.java:139)
>> at org.apache.xmlrpc.XmlRpcServer.execute(XmlRpcServer.java:125)
>> at org.apache.xmlrpc.WebServer$Connection.run(WebServer.java:761)
>> at org.apache.xmlrpc.WebServer$Runner.run(WebServer.java:642)
>> at java.lang.Thread.run(Thread.java:680)
>> org.apache.xmlrpc.XmlRpcException: java.lang.Exception:
>>org.apache.oodt.cas.filemgr.structs.exceptions.CatalogException: Failed
>>to perform complex query : null
>> at 
>>org.apache.xmlrpc.XmlRpcClientResponseProcessor.decodeException(XmlRpcCli
>>entResponseProcessor.java:104)
>> at 
>>org.apache.xmlrpc.XmlRpcClientResponseProcessor.decodeResponse(XmlRpcClie
>>ntResponseProcessor.java:71)
>> at 
>>org.apache.xmlrpc.XmlRpcClientWorker.execute(XmlRpcClientWorker.java:73)
>> at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:194)
>> at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:185)
>> at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:178)
>> at 
>>org.apache.oodt.cas.filemgr.system.XmlRpcFileManagerClient.complexQuery(X
>>mlRpcFileManagerClient.java:974)
>> at 
>>org.apache.oodt.cas.filemgr.tools.QueryTool.performSqlQuery(QueryTool.jav
>>a:252)
>> at org.apache.oodt.cas.filemgr.tools.QueryTool.main(QueryTool.java:242)
>> Exception in thread "main"
>>org.apache.oodt.cas.filemgr.structs.exceptions.CatalogException:
>>java.lang.Exception:
>>org.apache.oodt.cas.filemgr.structs.exceptions.CatalogException: Failed
>>to perform complex query : null
>> at 
>>org.apache.oodt.cas.filemgr.system.XmlRpcFileManagerClient.complexQuery(X
>>mlRpcFileManagerClient.java:980)
>> at 
>>org.apache.oodt.cas.filemgr.tools.QueryTool.performSqlQuery(QueryTool.jav
>>a:252)
>> at org.apache.oodt.cas.filemgr.tools.QueryTool.main(QueryTool.java:242)
>> 
>
>
>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>Chris Mattmann, Ph.D.
>Senior Computer Scientist
>NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
>Office: 171-266B, Mailstop: 171-246
>Email: chris.a.mattmann@nasa.gov
>WWW:   http://sunset.usc.edu/~mattmann/
>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>Adjunct Assistant Professor, Computer Science Department
>University of Southern California, Los Angeles, CA 90089 USA
>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>


Re: Issue with query_tool when all product types are not populated

Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hey Sean,

Interesting. Can you try with 0.3 and see if it gives you a different behavior? If it's a regression I'm happy to file an issue
and/or create a unit test for it.

Cheers,
Chris

On Feb 20, 2012, at 6:30 PM, Hardman, Sean H (388J) wrote:

> I first noticed this behavior in release 0.3 and just reaffirmed it in a latest and greatest build of 0.4-SNAPSHOT. To the best of my knowledge, this was not the case in previous versions. When querying a File Manager instance with a Lucene Catalog on the back end, the query_tool will throw an exception unless there is a product ingested for each product type listed in the policy (see the stack trace below).
> 
> I assume I am not the first person to notice this behavior. Is this worthy of a JIRA issue?
> 
> Thanks,
> Sean
> 
> 
> bash-3.2$ ./query_tool --url ${FILEMGR_URL} --sql -query "SELECT * FROM *"
> Feb 20, 2012 5:52:26 PM org.apache.oodt.cas.filemgr.catalog.LuceneCatalog paginateQuery
> WARNING: Query: [q=] for Product Type: [urn:pds:CatalogObject] returned no results
> java.lang.NullPointerException
> at org.apache.oodt.cas.filemgr.system.XmlRpcFileManager.complexQuery(XmlRpcFileManager.java:602)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.apache.xmlrpc.Invoker.execute(Invoker.java:130)
> at org.apache.xmlrpc.XmlRpcWorker.invokeHandler(XmlRpcWorker.java:84)
> at org.apache.xmlrpc.XmlRpcWorker.execute(XmlRpcWorker.java:146)
> at org.apache.xmlrpc.XmlRpcServer.execute(XmlRpcServer.java:139)
> at org.apache.xmlrpc.XmlRpcServer.execute(XmlRpcServer.java:125)
> at org.apache.xmlrpc.WebServer$Connection.run(WebServer.java:761)
> at org.apache.xmlrpc.WebServer$Runner.run(WebServer.java:642)
> at java.lang.Thread.run(Thread.java:680)
> org.apache.xmlrpc.XmlRpcException: java.lang.Exception: org.apache.oodt.cas.filemgr.structs.exceptions.CatalogException: Failed to perform complex query : null
> at org.apache.xmlrpc.XmlRpcClientResponseProcessor.decodeException(XmlRpcClientResponseProcessor.java:104)
> at org.apache.xmlrpc.XmlRpcClientResponseProcessor.decodeResponse(XmlRpcClientResponseProcessor.java:71)
> at org.apache.xmlrpc.XmlRpcClientWorker.execute(XmlRpcClientWorker.java:73)
> at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:194)
> at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:185)
> at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:178)
> at org.apache.oodt.cas.filemgr.system.XmlRpcFileManagerClient.complexQuery(XmlRpcFileManagerClient.java:974)
> at org.apache.oodt.cas.filemgr.tools.QueryTool.performSqlQuery(QueryTool.java:252)
> at org.apache.oodt.cas.filemgr.tools.QueryTool.main(QueryTool.java:242)
> Exception in thread "main" org.apache.oodt.cas.filemgr.structs.exceptions.CatalogException: java.lang.Exception: org.apache.oodt.cas.filemgr.structs.exceptions.CatalogException: Failed to perform complex query : null
> at org.apache.oodt.cas.filemgr.system.XmlRpcFileManagerClient.complexQuery(XmlRpcFileManagerClient.java:980)
> at org.apache.oodt.cas.filemgr.tools.QueryTool.performSqlQuery(QueryTool.java:252)
> at org.apache.oodt.cas.filemgr.tools.QueryTool.main(QueryTool.java:242)
> 


++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW:   http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++


Re: Issue with query_tool when all product types are not populated

Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hey Sean,

On Feb 23, 2012, at 12:24 PM, Hardman, Sean H (388J) wrote:

> Hey Chris,
> 
> I would love to prove that theory correct but I am not using variables to
> specify my policy directories. I am using absolute paths.

Ah, gotcha. Yeah the reason I thought it was ENV vars is that for whatever reason
the error message below indicates that it's trying to load policy (product types) out
of the file manager bin directory, look at the places in the log message that it's
trying to load:

>>> WARNING: XMLRepositoryManager: Unable to find product type: [convert_map
>>> filemgr filemgr-client migrate_xml_policy query_tool], returning null
>>> java.lang.NullPointerException

Those are all the filemgr bin script dir contents. So that's what made me think there was
a blank somewhere in there, which usually is the result of an unset env var being referenced
in the repo path load.

> Your reply did
> prompt me to run through the tests again and I did discover something in
> the filemgr-client script. In April of last year, I created an issue [1]
> regarding the query_tool script and its lack of support for quoted
> parameters. The resolution was to replace $* in the script with "$@". Now
> that the filemgr-client script needs to support the same arguments that
> the query_tool script supports, I am thinking it needs the same patch as
> well.

+1, agreed. What shell are you using? Most of the FM script stuff is 
tested in tsch, but I think it may have issues in bash. Yes, I know, 
bash is more common -- shoot me I'm different :)

> I made that change locally and although the query still fails as
> documented in [2], the error below that you reference no longer is
> generated by the server.

+1, seems like it fixed that part then, so +1 to JIRA issue.

> I am not entirely clear on the connection between
> this patch and the original error (maybe you or Brian could enlighten me),
> but it does appear worthy of a new JIRA issue.

Well, see above, that's what tipped me off. Not sure why it's not working
that way per [2], but we should definitely file a JIRA issue RE: your local
changes and patching the FM client script. At some point I'd love to make
that more Nutch like (see [3]), but just haven't had the cycles to do so yet.
In doing so, we could eliminate the need for an fm-client script, and simply
have a script, e.g., "filemgr", where you can:

./filemgr server <server cmd + options>
./filemgr client <client cmd + options>
./filemgr <specific tool class> <specific tool options>

HTH,
Chris

> 
> Sean
> 
> [1] https://issues.apache.org/jira/browse/OODT-185
> [2] https://issues.apache.org/jira/browse/OODT-384
[3] http://svn.apache.org/repos/asf/nutch/trunk/src/bin/nutch

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW:   http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++


Re: Issue with query_tool when all product types are not populated

Posted by "Hardman, Sean H (388J)" <se...@jpl.nasa.gov>.
Hey Chris,

I would love to prove that theory correct but I am not using variables to
specify my policy directories. I am using absolute paths. Your reply did
prompt me to run through the tests again and I did discover something in
the filemgr-client script. In April of last year, I created an issue [1]
regarding the query_tool script and its lack of support for quoted
parameters. The resolution was to replace $* in the script with "$@". Now
that the filemgr-client script needs to support the same arguments that
the query_tool script supports, I am thinking it needs the same patch as
well. I made that change locally and although the query still fails as
documented in [2], the error below that you reference no longer is
generated by the server. I am not entirely clear on the connection between
this patch and the original error (maybe you or Brian could enlighten me),
but it does appear worthy of a new JIRA issue.

Sean

[1] https://issues.apache.org/jira/browse/OODT-185
[2] https://issues.apache.org/jira/browse/OODT-384

On 2/23/12 6:21 AM, "Mattmann, Chris A (388J)"
<ch...@jpl.nasa.gov> wrote:

>Hey Sean,
>
>Thanks, the below helped, as I think I know now what your problem is.
>Fast forward to here:
>
>On Feb 21, 2012, at 11:01 AM, Hardman, Sean H (388J) wrote:
>> 
>> And generates the following on the server side:
>> 
>> Feb 21, 2012 9:32:29 AM
>> org.apache.oodt.cas.filemgr.repository.XMLRepositoryManager
>> getProductTypeByName
>> WARNING: XMLRepositoryManager: Unable to find product type: [convert_map
>> filemgr filemgr-client migrate_xml_policy query_tool], returning null
>> java.lang.NullPointerException
>
>This looks like an incorrect ENV var issue, where you assumed in your
>product type policy that a particular environment variable was present
>when you started file manager, but in the end, it wasn't and you defaulted
>to the current directory (which looks like bin) where you started file
>manager
>from as your policy directory.
>
>Can you please confirm that your product type repository path for these
>three references an environment variable that is actually present when you
>started the file manager? One way to do this is to simply make sure it's
>there
>explicitly in the session (via export or setenv) and then ./filemgr
>restart.
>
>HTH,
>Chris
>
>> 
>> On 2/20/12 11:45 PM, "Brian Foster" <ho...@me.com> wrote:
>> 
>>> Hey Sean,
>>> 
>>> Try using the new SqlQuery action in 0.4 filemgr
>>> 
>>> -Brian 
>>> 
>>> On Feb 20, 2012, at 6:30 PM, "Hardman, Sean H (388J)"
>>> <se...@jpl.nasa.gov> wrote:
>>> 
>>>> I first noticed this behavior in release 0.3 and just reaffirmed it in
>>>> a latest and greatest build of 0.4-SNAPSHOT. To the best of my
>>>> knowledge, this was not the case in previous versions. When querying a
>>>> File Manager instance with a Lucene Catalog on the back end, the
>>>> query_tool will throw an exception unless there is a product ingested
>>>> for each product type listed in the policy (see the stack trace
>>>>below).
>>>> 
>>>> I assume I am not the first person to notice this behavior. Is this
>>>> worthy of a JIRA issue?
>>>> 
>>>> Thanks,
>>>> Sean
>>>> 
>>>> 
>>>> bash-3.2$ ./query_tool --url ${FILEMGR_URL} --sql -query "SELECT *
>>>>FROM
>>>> *"
>>>> Feb 20, 2012 5:52:26 PM
>>>> org.apache.oodt.cas.filemgr.catalog.LuceneCatalog paginateQuery
>>>> WARNING: Query: [q=] for Product Type: [urn:pds:CatalogObject]
>>>>returned
>>>> no results
>>>> java.lang.NullPointerException
>>>> at 
>>>> 
>>>>org.apache.oodt.cas.filemgr.system.XmlRpcFileManager.complexQuery(XmlRp
>>>>cF
>>>> ileManager.java:602)
>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>> at 
>>>> 
>>>>sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.ja
>>>>va
>>>> :39)
>>>> at 
>>>> 
>>>>sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccesso
>>>>rI
>>>> mpl.java:25)
>>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>> at org.apache.xmlrpc.Invoker.execute(Invoker.java:130)
>>>> at org.apache.xmlrpc.XmlRpcWorker.invokeHandler(XmlRpcWorker.java:84)
>>>> at org.apache.xmlrpc.XmlRpcWorker.execute(XmlRpcWorker.java:146)
>>>> at org.apache.xmlrpc.XmlRpcServer.execute(XmlRpcServer.java:139)
>>>> at org.apache.xmlrpc.XmlRpcServer.execute(XmlRpcServer.java:125)
>>>> at org.apache.xmlrpc.WebServer$Connection.run(WebServer.java:761)
>>>> at org.apache.xmlrpc.WebServer$Runner.run(WebServer.java:642)
>>>> at java.lang.Thread.run(Thread.java:680)
>>>> org.apache.xmlrpc.XmlRpcException: java.lang.Exception:
>>>> org.apache.oodt.cas.filemgr.structs.exceptions.CatalogException:
>>>>Failed
>>>> to perform complex query : null
>>>> at 
>>>> 
>>>>org.apache.xmlrpc.XmlRpcClientResponseProcessor.decodeException(XmlRpcC
>>>>li
>>>> entResponseProcessor.java:104)
>>>> at 
>>>> 
>>>>org.apache.xmlrpc.XmlRpcClientResponseProcessor.decodeResponse(XmlRpcCl
>>>>ie
>>>> ntResponseProcessor.java:71)
>>>> at 
>>>> 
>>>>org.apache.xmlrpc.XmlRpcClientWorker.execute(XmlRpcClientWorker.java:73
>>>>)
>>>> at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:194)
>>>> at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:185)
>>>> at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:178)
>>>> at 
>>>> 
>>>>org.apache.oodt.cas.filemgr.system.XmlRpcFileManagerClient.complexQuery
>>>>(X
>>>> mlRpcFileManagerClient.java:974)
>>>> at 
>>>> 
>>>>org.apache.oodt.cas.filemgr.tools.QueryTool.performSqlQuery(QueryTool.j
>>>>av
>>>> a:252)
>>>> at 
>>>>org.apache.oodt.cas.filemgr.tools.QueryTool.main(QueryTool.java:242)
>>>> Exception in thread "main"
>>>> org.apache.oodt.cas.filemgr.structs.exceptions.CatalogException:
>>>> java.lang.Exception:
>>>> org.apache.oodt.cas.filemgr.structs.exceptions.CatalogException:
>>>>Failed
>>>> to perform complex query : null
>>>> at 
>>>> 
>>>>org.apache.oodt.cas.filemgr.system.XmlRpcFileManagerClient.complexQuery
>>>>(X
>>>> mlRpcFileManagerClient.java:980)
>>>> at 
>>>> 
>>>>org.apache.oodt.cas.filemgr.tools.QueryTool.performSqlQuery(QueryTool.j
>>>>av
>>>> a:252)
>>>> at 
>>>>org.apache.oodt.cas.filemgr.tools.QueryTool.main(QueryTool.java:242)
>>>> 
>> 
>
>
>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>Chris Mattmann, Ph.D.
>Senior Computer Scientist
>NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
>Office: 171-266B, Mailstop: 171-246
>Email: chris.a.mattmann@nasa.gov
>WWW:   http://sunset.usc.edu/~mattmann/
>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>Adjunct Assistant Professor, Computer Science Department
>University of Southern California, Los Angeles, CA 90089 USA
>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>


Re: Issue with query_tool when all product types are not populated

Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.
Hey Sean,

Thanks, the below helped, as I think I know now what your problem is.
Fast forward to here:

On Feb 21, 2012, at 11:01 AM, Hardman, Sean H (388J) wrote:
> 
> And generates the following on the server side:
> 
> Feb 21, 2012 9:32:29 AM
> org.apache.oodt.cas.filemgr.repository.XMLRepositoryManager
> getProductTypeByName
> WARNING: XMLRepositoryManager: Unable to find product type: [convert_map
> filemgr filemgr-client migrate_xml_policy query_tool], returning null
> java.lang.NullPointerException

This looks like an incorrect ENV var issue, where you assumed in your
product type policy that a particular environment variable was present
when you started file manager, but in the end, it wasn't and you defaulted
to the current directory (which looks like bin) where you started file manager
from as your policy directory.

Can you please confirm that your product type repository path for these 
three references an environment variable that is actually present when you
started the file manager? One way to do this is to simply make sure it's there
explicitly in the session (via export or setenv) and then ./filemgr restart.

HTH,
Chris

> 
> On 2/20/12 11:45 PM, "Brian Foster" <ho...@me.com> wrote:
> 
>> Hey Sean,
>> 
>> Try using the new SqlQuery action in 0.4 filemgr
>> 
>> -Brian 
>> 
>> On Feb 20, 2012, at 6:30 PM, "Hardman, Sean H (388J)"
>> <se...@jpl.nasa.gov> wrote:
>> 
>>> I first noticed this behavior in release 0.3 and just reaffirmed it in
>>> a latest and greatest build of 0.4-SNAPSHOT. To the best of my
>>> knowledge, this was not the case in previous versions. When querying a
>>> File Manager instance with a Lucene Catalog on the back end, the
>>> query_tool will throw an exception unless there is a product ingested
>>> for each product type listed in the policy (see the stack trace below).
>>> 
>>> I assume I am not the first person to notice this behavior. Is this
>>> worthy of a JIRA issue?
>>> 
>>> Thanks,
>>> Sean
>>> 
>>> 
>>> bash-3.2$ ./query_tool --url ${FILEMGR_URL} --sql -query "SELECT * FROM
>>> *"
>>> Feb 20, 2012 5:52:26 PM
>>> org.apache.oodt.cas.filemgr.catalog.LuceneCatalog paginateQuery
>>> WARNING: Query: [q=] for Product Type: [urn:pds:CatalogObject] returned
>>> no results
>>> java.lang.NullPointerException
>>> at 
>>> org.apache.oodt.cas.filemgr.system.XmlRpcFileManager.complexQuery(XmlRpcF
>>> ileManager.java:602)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at 
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java
>>> :39)
>>> at 
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorI
>>> mpl.java:25)
>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>> at org.apache.xmlrpc.Invoker.execute(Invoker.java:130)
>>> at org.apache.xmlrpc.XmlRpcWorker.invokeHandler(XmlRpcWorker.java:84)
>>> at org.apache.xmlrpc.XmlRpcWorker.execute(XmlRpcWorker.java:146)
>>> at org.apache.xmlrpc.XmlRpcServer.execute(XmlRpcServer.java:139)
>>> at org.apache.xmlrpc.XmlRpcServer.execute(XmlRpcServer.java:125)
>>> at org.apache.xmlrpc.WebServer$Connection.run(WebServer.java:761)
>>> at org.apache.xmlrpc.WebServer$Runner.run(WebServer.java:642)
>>> at java.lang.Thread.run(Thread.java:680)
>>> org.apache.xmlrpc.XmlRpcException: java.lang.Exception:
>>> org.apache.oodt.cas.filemgr.structs.exceptions.CatalogException: Failed
>>> to perform complex query : null
>>> at 
>>> org.apache.xmlrpc.XmlRpcClientResponseProcessor.decodeException(XmlRpcCli
>>> entResponseProcessor.java:104)
>>> at 
>>> org.apache.xmlrpc.XmlRpcClientResponseProcessor.decodeResponse(XmlRpcClie
>>> ntResponseProcessor.java:71)
>>> at 
>>> org.apache.xmlrpc.XmlRpcClientWorker.execute(XmlRpcClientWorker.java:73)
>>> at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:194)
>>> at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:185)
>>> at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:178)
>>> at 
>>> org.apache.oodt.cas.filemgr.system.XmlRpcFileManagerClient.complexQuery(X
>>> mlRpcFileManagerClient.java:974)
>>> at 
>>> org.apache.oodt.cas.filemgr.tools.QueryTool.performSqlQuery(QueryTool.jav
>>> a:252)
>>> at org.apache.oodt.cas.filemgr.tools.QueryTool.main(QueryTool.java:242)
>>> Exception in thread "main"
>>> org.apache.oodt.cas.filemgr.structs.exceptions.CatalogException:
>>> java.lang.Exception:
>>> org.apache.oodt.cas.filemgr.structs.exceptions.CatalogException: Failed
>>> to perform complex query : null
>>> at 
>>> org.apache.oodt.cas.filemgr.system.XmlRpcFileManagerClient.complexQuery(X
>>> mlRpcFileManagerClient.java:980)
>>> at 
>>> org.apache.oodt.cas.filemgr.tools.QueryTool.performSqlQuery(QueryTool.jav
>>> a:252)
>>> at org.apache.oodt.cas.filemgr.tools.QueryTool.main(QueryTool.java:242)
>>> 
> 


++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW:   http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++


Re: Issue with query_tool when all product types are not populated

Posted by "Hardman, Sean H (388J)" <se...@jpl.nasa.gov>.
Hey Brian,

Thanks for pointing out that new feature in the FM client. Unfortunately,
it did not work any better for me. To reset the environment, I have three
product types defined in my policy but only one file ingested for the
CatalogFile product type.

% ./filemgr-client --url http://localhost:9000 --operation --sqlQuery
-query "SELECT * FROM *"

Generates the following on the client side:

Feb 21, 2012 9:32:29 AM
org.apache.oodt.cas.filemgr.system.XmlRpcFileManagerClient <init>
INFO: Loading File Manager Configuration Properties from:
[../etc/filemgr.properties]
org.apache.xmlrpc.XmlRpcException: java.lang.Exception:
org.apache.oodt.cas.filemgr.structs.exceptions.CatalogException: Failed to
perform complex query : null
...

And generates the following on the server side:

Feb 21, 2012 9:32:29 AM
org.apache.oodt.cas.filemgr.repository.XMLRepositoryManager
getProductTypeByName
WARNING: XMLRepositoryManager: Unable to find product type: [convert_map
filemgr filemgr-client migrate_xml_policy query_tool], returning null
java.lang.NullPointerException
...


I can provide full stack traces on request. In addition where I mimic the
successful query_tool query by limiting the query to the CatalogFile
product type as follows:

% ./filemgr-client --url http://localhost:9000 --operation --sqlQuery
-query "SELECT * FROM CatalogFile"


The client generated the same stack trace although the server did return 1
desired result:

Feb 21, 2012 9:57:55 AM
org.apache.oodt.cas.filemgr.system.XmlRpcFileManager complexQuery
INFO: Query returned 1 results


Thanks,
Sean

On 2/20/12 11:45 PM, "Brian Foster" <ho...@me.com> wrote:

>Hey Sean,
>
>Try using the new SqlQuery action in 0.4 filemgr
>
>-Brian 
>
>On Feb 20, 2012, at 6:30 PM, "Hardman, Sean H (388J)"
><se...@jpl.nasa.gov> wrote:
>
>> I first noticed this behavior in release 0.3 and just reaffirmed it in
>>a latest and greatest build of 0.4-SNAPSHOT. To the best of my
>>knowledge, this was not the case in previous versions. When querying a
>>File Manager instance with a Lucene Catalog on the back end, the
>>query_tool will throw an exception unless there is a product ingested
>>for each product type listed in the policy (see the stack trace below).
>> 
>> I assume I am not the first person to notice this behavior. Is this
>>worthy of a JIRA issue?
>> 
>> Thanks,
>> Sean
>> 
>> 
>> bash-3.2$ ./query_tool --url ${FILEMGR_URL} --sql -query "SELECT * FROM
>>*"
>> Feb 20, 2012 5:52:26 PM
>>org.apache.oodt.cas.filemgr.catalog.LuceneCatalog paginateQuery
>> WARNING: Query: [q=] for Product Type: [urn:pds:CatalogObject] returned
>>no results
>> java.lang.NullPointerException
>> at 
>>org.apache.oodt.cas.filemgr.system.XmlRpcFileManager.complexQuery(XmlRpcF
>>ileManager.java:602)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at 
>>sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java
>>:39)
>> at 
>>sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorI
>>mpl.java:25)
>> at java.lang.reflect.Method.invoke(Method.java:597)
>> at org.apache.xmlrpc.Invoker.execute(Invoker.java:130)
>> at org.apache.xmlrpc.XmlRpcWorker.invokeHandler(XmlRpcWorker.java:84)
>> at org.apache.xmlrpc.XmlRpcWorker.execute(XmlRpcWorker.java:146)
>> at org.apache.xmlrpc.XmlRpcServer.execute(XmlRpcServer.java:139)
>> at org.apache.xmlrpc.XmlRpcServer.execute(XmlRpcServer.java:125)
>> at org.apache.xmlrpc.WebServer$Connection.run(WebServer.java:761)
>> at org.apache.xmlrpc.WebServer$Runner.run(WebServer.java:642)
>> at java.lang.Thread.run(Thread.java:680)
>> org.apache.xmlrpc.XmlRpcException: java.lang.Exception:
>>org.apache.oodt.cas.filemgr.structs.exceptions.CatalogException: Failed
>>to perform complex query : null
>> at 
>>org.apache.xmlrpc.XmlRpcClientResponseProcessor.decodeException(XmlRpcCli
>>entResponseProcessor.java:104)
>> at 
>>org.apache.xmlrpc.XmlRpcClientResponseProcessor.decodeResponse(XmlRpcClie
>>ntResponseProcessor.java:71)
>> at 
>>org.apache.xmlrpc.XmlRpcClientWorker.execute(XmlRpcClientWorker.java:73)
>> at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:194)
>> at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:185)
>> at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:178)
>> at 
>>org.apache.oodt.cas.filemgr.system.XmlRpcFileManagerClient.complexQuery(X
>>mlRpcFileManagerClient.java:974)
>> at 
>>org.apache.oodt.cas.filemgr.tools.QueryTool.performSqlQuery(QueryTool.jav
>>a:252)
>> at org.apache.oodt.cas.filemgr.tools.QueryTool.main(QueryTool.java:242)
>> Exception in thread "main"
>>org.apache.oodt.cas.filemgr.structs.exceptions.CatalogException:
>>java.lang.Exception:
>>org.apache.oodt.cas.filemgr.structs.exceptions.CatalogException: Failed
>>to perform complex query : null
>> at 
>>org.apache.oodt.cas.filemgr.system.XmlRpcFileManagerClient.complexQuery(X
>>mlRpcFileManagerClient.java:980)
>> at 
>>org.apache.oodt.cas.filemgr.tools.QueryTool.performSqlQuery(QueryTool.jav
>>a:252)
>> at org.apache.oodt.cas.filemgr.tools.QueryTool.main(QueryTool.java:242)
>> 


Re: Issue with query_tool when all product types are not populated

Posted by Brian Foster <ho...@me.com>.
Hey Sean,

Try using the new SqlQuery action in 0.4 filemgr

-Brian 

On Feb 20, 2012, at 6:30 PM, "Hardman, Sean H (388J)" <se...@jpl.nasa.gov> wrote:

> I first noticed this behavior in release 0.3 and just reaffirmed it in a latest and greatest build of 0.4-SNAPSHOT. To the best of my knowledge, this was not the case in previous versions. When querying a File Manager instance with a Lucene Catalog on the back end, the query_tool will throw an exception unless there is a product ingested for each product type listed in the policy (see the stack trace below).
> 
> I assume I am not the first person to notice this behavior. Is this worthy of a JIRA issue?
> 
> Thanks,
> Sean
> 
> 
> bash-3.2$ ./query_tool --url ${FILEMGR_URL} --sql -query "SELECT * FROM *"
> Feb 20, 2012 5:52:26 PM org.apache.oodt.cas.filemgr.catalog.LuceneCatalog paginateQuery
> WARNING: Query: [q=] for Product Type: [urn:pds:CatalogObject] returned no results
> java.lang.NullPointerException
> at org.apache.oodt.cas.filemgr.system.XmlRpcFileManager.complexQuery(XmlRpcFileManager.java:602)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.apache.xmlrpc.Invoker.execute(Invoker.java:130)
> at org.apache.xmlrpc.XmlRpcWorker.invokeHandler(XmlRpcWorker.java:84)
> at org.apache.xmlrpc.XmlRpcWorker.execute(XmlRpcWorker.java:146)
> at org.apache.xmlrpc.XmlRpcServer.execute(XmlRpcServer.java:139)
> at org.apache.xmlrpc.XmlRpcServer.execute(XmlRpcServer.java:125)
> at org.apache.xmlrpc.WebServer$Connection.run(WebServer.java:761)
> at org.apache.xmlrpc.WebServer$Runner.run(WebServer.java:642)
> at java.lang.Thread.run(Thread.java:680)
> org.apache.xmlrpc.XmlRpcException: java.lang.Exception: org.apache.oodt.cas.filemgr.structs.exceptions.CatalogException: Failed to perform complex query : null
> at org.apache.xmlrpc.XmlRpcClientResponseProcessor.decodeException(XmlRpcClientResponseProcessor.java:104)
> at org.apache.xmlrpc.XmlRpcClientResponseProcessor.decodeResponse(XmlRpcClientResponseProcessor.java:71)
> at org.apache.xmlrpc.XmlRpcClientWorker.execute(XmlRpcClientWorker.java:73)
> at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:194)
> at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:185)
> at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:178)
> at org.apache.oodt.cas.filemgr.system.XmlRpcFileManagerClient.complexQuery(XmlRpcFileManagerClient.java:974)
> at org.apache.oodt.cas.filemgr.tools.QueryTool.performSqlQuery(QueryTool.java:252)
> at org.apache.oodt.cas.filemgr.tools.QueryTool.main(QueryTool.java:242)
> Exception in thread "main" org.apache.oodt.cas.filemgr.structs.exceptions.CatalogException: java.lang.Exception: org.apache.oodt.cas.filemgr.structs.exceptions.CatalogException: Failed to perform complex query : null
> at org.apache.oodt.cas.filemgr.system.XmlRpcFileManagerClient.complexQuery(XmlRpcFileManagerClient.java:980)
> at org.apache.oodt.cas.filemgr.tools.QueryTool.performSqlQuery(QueryTool.java:252)
> at org.apache.oodt.cas.filemgr.tools.QueryTool.main(QueryTool.java:242)
>