[
https://issues.apache.org/jira/browse/OOZIE-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15675685#comment-15675685
]
Abhishek Bafna commented on OOZIE-2225:
---------------------------------------
[~jaydeepvishwakarma] It will be required, as {{isEnabled}} controls that
{{seletStr}} should be added or not. In the case of {{FILTER_TEXT}} it is not
updating the flag, it does uses the flag while prefixing {{seletStr}} into
{{filterJobsUsingText}} method. Here is the wrong query it will generate
otherwise.
{code}
"Select w.id, w.appName, w.appPath, w.conf, w.statusStr, w.kickoffTimestamp,
w.startTimestamp, w.endTimestamp, w.pauseTimestamp, w.createdTimestamp, w.user,
w.group, w.timeUnitStr, w.timeOut from BundleJobBean w where (w.appName LIKE
:text1 OR w.user LIKE :text2 OR w.id = :text3)Select w.id, w.appName,
w.appPath, w.conf, w.statusStr, w.kickoffTimestamp, w.startTimestamp,
w.endTimestamp, w.pauseTimestamp, w.createdTimestamp, w.user, w.group,
w.timeUnitStr, w.timeOut from BundleJobBean w where w.statusStr IN (:status0)
order by w.createdTimestamp desc".
{code}
It has generated the two select query for status and text.
> Add wild card filter for gathering jobs
> ---------------------------------------
>
> Key: OOZIE-2225
> URL: https://issues.apache.org/jira/browse/OOZIE-2225
> Project: Oozie
> Issue Type: Improvement
> Components: core
> Affects Versions: 4.1.0
> Reporter: Sai Chirravuri
> Assignee: Peter Bacsko
> Fix For: trunk
>
> Attachments: OOZIE-2225-001.patch, OOZIE-2225-002.patch,
> OOZIE-2225-003.patch, OOZIE-2225-004.patch, OOZIE-2225-005.patch,
> OOZIE-2225-007.patch, OOZIE-2225-008.patch, OOZIE-2225-009.patch,
> OOZIE-2225-010.patch, OOZIE-2225-amend-001.patch, OOZIE-2225-amend-002.patch
>
>
> Oozie currently supports name, user, group, status, frequency and unit as
> filter params.
> Add wild card param that matches partially with name/user or complete match
> with ID
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
