You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Bob Liu (Created) (JIRA)" <ji...@apache.org> on 2012/01/19 01:52:39 UTC
[jira] [Created] (OOZIE-656) Jobs search filters do not work on CLI
Jobs search filters do not work on CLI
--------------------------------------
Key: OOZIE-656
URL: https://issues.apache.org/jira/browse/OOZIE-656
Project: Oozie
Issue Type: Bug
Environment: Oozie 3.0.2
Reporter: Bob Liu
When you specify multiple filters like the following on the CLI, it basically ignores the filter(s) after the ";" and returns all jobs owned by user "user1" and ignoring the "status" filter specified. However, the custom filter via Oozie web console seems to work just fine.
oozie jobs -filter user=user1;status=KILLED
--
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
Re: [jira] [Commented] (OOZIE-656) Jobs search filters do not work on CLI
Posted by KIRAN <nk...@gmail.com>.
Hi Bob Liu,
Could you please try enclosing all the filters within double quotes
like this -->
"user=user1;status=KILLED"
Thanks,
Kiran
On Wed, Jan 18, 2012 at 5:00 PM, Virag Kothari (Commented) (JIRA) <
jira@apache.org> wrote:
>
> [
> https://issues.apache.org/jira/browse/OOZIE-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13188857#comment-13188857]
>
> Virag Kothari commented on OOZIE-656:
> -------------------------------------
>
> The semicolon separating the filter is a Bash reserved character. You must
> escape it by either quoting the string, or escaping the semicolon with a
> backslash.
>
> Can you try: oozie jobs -filter user=user1\;status=KILLED
>
> > Jobs search filters do not work on CLI
> > --------------------------------------
> >
> > Key: OOZIE-656
> > URL: https://issues.apache.org/jira/browse/OOZIE-656
> > Project: Oozie
> > Issue Type: Bug
> > Environment: Oozie 3.0.2
> > Reporter: Bob Liu
> >
> > When you specify multiple filters like the following on the CLI, it
> basically ignores the filter(s) after the ";" and returns all jobs owned by
> user "user1" and ignoring the "status" filter specified. However, the
> custom filter via Oozie web console seems to work just fine.
> > oozie jobs -filter user=user1;status=KILLED
>
> --
> 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] [Closed] (OOZIE-656) Jobs search filters do not work on CLI
Posted by "Bob Liu (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bob Liu closed OOZIE-656.
-------------------------
Resolution: Not A Problem
Worksform...
> Jobs search filters do not work on CLI
> --------------------------------------
>
> Key: OOZIE-656
> URL: https://issues.apache.org/jira/browse/OOZIE-656
> Project: Oozie
> Issue Type: Bug
> Environment: Oozie 3.0.2
> Reporter: Bob Liu
>
> When you specify multiple filters like the following on the CLI, it basically ignores the filter(s) after the ";" and returns all jobs owned by user "user1" and ignoring the "status" filter specified. However, the custom filter via Oozie web console seems to work just fine.
> oozie jobs -filter user=user1;status=KILLED
--
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] [Commented] (OOZIE-656) Jobs search filters do not work on
CLI
Posted by "Virag Kothari (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13188857#comment-13188857 ]
Virag Kothari commented on OOZIE-656:
-------------------------------------
The semicolon separating the filter is a Bash reserved character. You must escape it by either quoting the string, or escaping the semicolon with a backslash.
Can you try: oozie jobs -filter user=user1\;status=KILLED
> Jobs search filters do not work on CLI
> --------------------------------------
>
> Key: OOZIE-656
> URL: https://issues.apache.org/jira/browse/OOZIE-656
> Project: Oozie
> Issue Type: Bug
> Environment: Oozie 3.0.2
> Reporter: Bob Liu
>
> When you specify multiple filters like the following on the CLI, it basically ignores the filter(s) after the ";" and returns all jobs owned by user "user1" and ignoring the "status" filter specified. However, the custom filter via Oozie web console seems to work just fine.
> oozie jobs -filter user=user1;status=KILLED
--
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] [Commented] (OOZIE-656) Jobs search filters do not work on
CLI
Posted by "Bob Liu (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13188992#comment-13188992 ]
Bob Liu commented on OOZIE-656:
-------------------------------
Yes... escaping ";" works... just wondering why can't you guys just change the delimiter to something else like a comma or a colon?
> Jobs search filters do not work on CLI
> --------------------------------------
>
> Key: OOZIE-656
> URL: https://issues.apache.org/jira/browse/OOZIE-656
> Project: Oozie
> Issue Type: Bug
> Environment: Oozie 3.0.2
> Reporter: Bob Liu
>
> When you specify multiple filters like the following on the CLI, it basically ignores the filter(s) after the ";" and returns all jobs owned by user "user1" and ignoring the "status" filter specified. However, the custom filter via Oozie web console seems to work just fine.
> oozie jobs -filter user=user1;status=KILLED
--
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