+1 to writing some unit tests for this *grin*
Cheers,
Chris
On Feb 25, 2012, at 1:37 AM, Brian Foster wrote:
>
> Actually the command line parses it and removes the quotes, then the
> shell is getting it without quotes and thus expands it, then java it getting
> it and parses it... it
Actually the command line parses it and removes the quotes, then the shell
is getting it without quotes and thus expands it, then java it getting it and
parses it... it's an actual nightmare to deal with... I believe it was John
Geiselman (spelling?) who showed me how to make quey_tool hand
Hey Sean,
Ya I'd expect query_tool to work in this case and filemgr-client with CLI to
not because the query_tool script reads in its argument differently than
filemgr-client script... Just a sucky shell side-affect... maybe we can change
the filemgr-client script to read arguments the same way
Hey Brian,
I definitely agree with you, something is being expanded or replaced but
like Chris eluded to, I think it has something to do with the environment.
I am using Bourne shell in OS X which is the environment where I
discovered the problem related to [1]. It looks to me to be a similar
issu
hmm i take that back. $@ seems to do the trick
On Feb 23, 2012, at 2:32 PM, Nguyen, Ricky wrote:
> I've run into this issue with using filemgr-client CLI. I think when the
> WHERE clause is empty or missing, the parser is trying to send NULL values
> (as the search criteria) over xmlrpc.
>
> Q
I've run into this issue with using filemgr-client CLI. I think when the WHERE
clause is empty or missing, the parser is trying to send NULL values (as the
search criteria) over xmlrpc.
Query tool appears to work with "SELECT * FROM MyProductType"
-Ricky
On Feb 23, 2012, at 1:29 PM, holenoter
hey sean,this part of your log output tells me your shell is expanding your *'s: WARNING: XMLRepositoryManager: Unable to find product type:[convert_map filemgr filemgr-client migrate_xml_policy query_tool], returning null -brianOn Feb 23, 2012, at 01:16 PM, "Hardman, Sean H (388J)" wr
hey sean,try it with query_tool... it takes its args in differently than filemgr-client-brianOn Feb 23, 2012, at 01:16 PM, "Hardman, Sean H (388J)" wrote:Hey Brian,
Restoring to the original filemgr-client script (using $* instead of
"$@"), I get the same result with single or double quotes.
Sea
Hey Brian,
Restoring to the original filemgr-client script (using $* instead of
"$@"), I get the same result with single or double quotes.
Sean
On 2/23/12 11:47 AM, "Brian Foster" wrote:
>Hey Sean,
>
>Maybe try using single quotes instead of double... i.e. ... -query
>'SELECT * FROM *'... your
NICE, bfost. That could be it!
Cheers,
Chris
On Feb 23, 2012, at 12:47 PM, Brian Foster wrote:
> Hey Sean,
>
> Maybe try using single quotes instead of double... i.e. ... -query 'SELECT *
> FROM *'... your shell is prob expanding your *'s
>
> -Brian
>
> "Hardman, Sean H (388J)" wrote:
>
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
Tried single,double and no quotes. In all cases SELECT * did not work. But
it works if I specify the element name or the product-type.
On Thu, Feb 23, 2012 at 11:47 AM, Brian Foster wrote:
> Hey Sean,
>
> Maybe try using single quotes instead of double... i.e. ... -query 'SELECT
> * FROM *'... y
Hey Sean,
Maybe try using single quotes instead of double... i.e. ... -query 'SELECT *
FROM *'... your shell is prob expanding your *'s
-Brian
"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 director
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 issu
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.mattm...@jpl.nasa.gov> wrote:
>
>> Th
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.XMLRepositor
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.mattm...@jpl.nasa.gov> wrote:
> Thanks for the case Sheryl. Would you mind filing a JIRA issue for 0.5 to
> investigate this?
>
> Cheers,
> Ch
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 '
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
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 i
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:
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 th
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)"
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
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 an
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 e
25 matches
Mail list logo
