Re: jobbrowser oozie didn't not match query condition

7 views
Skip to first unread message

钟老五

unread,
Dec 4, 2017, 1:31:39 AM12/4/17
to via Hue-Users
Hi,all
 
   Job Browser  ’s  Workflows / Schedulers/ Bundles  will send query to oozie server. But I seems that the query request doesn’t match the search condition .



when I click Workflows / Schedulers/ Bundles   button, I get request in log:


GET /oozie/v1/jobs?len=100&doAs=zpdn1691&filter=startcreatedtime%3D-7d&offset=1&timezone=Asia%2FShanghai&jobtype=wf HTTP/1.1” 400 968

GET /oozie/v1/jobs?len=100&doAs=zpdn1691&filter=startcreatedtime%3D-7d&offset=1&timezone=Asia%2FShanghai&jobtype=coord HTTP/1.1" 400 968

GET /oozie/v1/jobs?len=100&doAs=zpdn1691&filter=startcreatedtime%3D-7d&offset=1&timezone=Asia%2FShanghai&jobtype=bundle HTTP/1.1" 400 968





And I check  the request by postman and found that some parameters result in the error.


when "jobtype=wf"   doAs=xxx  result in error.

when “jobtype=bundle"   doAs=xxx and startcreatedtime=xxx  result in error.

when "jobtype=wf"   doAs=xxx startcreatedtime=xxx  result in error.


It seems the result have something to do with oozie version. And I check  the api document.


There is no parameter about “doAs” , and “startCreatedTime” sometimes not work.


Maybe the request could change from doAs=cloudera to filter=user%3Dcloudera.









钟老五

unread,
Dec 4, 2017, 1:34:17 AM12/4/17
to via Hue-Users
My hue version is   4.0

and oozie server version is  4.1.0-cdh5.6.0


在 2017年12月4日,下午2:31,钟老五 <zhong...@gmail.com> 写道:

Hi,all
 
   Job Browser  ’s  Workflows / Schedulers/ Bundles  will send query to oozie server. But I seems that the query request doesn’t match the search condition .


<PastedGraphic-6.tiff>

when I click Workflows / Schedulers/ Bundles   button, I get request in log:


GET /oozie/v1/jobs?len=100&doAs=zpdn1691&filter=startcreatedtime%3D-7d&offset=1&timezone=Asia%2FShanghai&jobtype=wf HTTP/1.1” 400 968

GET /oozie/v1/jobs?len=100&doAs=zpdn1691&filter=startcreatedtime%3D-7d&offset=1&timezone=Asia%2FShanghai&jobtype=coord HTTP/1.1" 400 968

GET /oozie/v1/jobs?len=100&doAs=zpdn1691&filter=startcreatedtime%3D-7d&offset=1&timezone=Asia%2FShanghai&jobtype=bundle HTTP/1.1" 400 968


<PastedGraphic-9.tiff>



And I check  the request by postman and found that some parameters result in the error.


when "jobtype=wf"   doAs=xxx  result in error.

when “jobtype=bundle"   doAs=xxx and startcreatedtime=xxx  result in error.

when "jobtype=wf"   doAs=xxx startcreatedtime=xxx  result in error.

It seems the result have something to do with oozie version. And I check  the api document.


There is no parameter about “doAs” , and “startCreatedTime” sometimes not work.


Maybe the request could change from doAs=cloudera to filter=user%3Dcloudera.


<PastedGraphic-7.tiff>



<PastedGraphic-8.tiff>





钟老五

unread,
Dec 4, 2017, 3:03:06 AM12/4/17
to via Hue-Users
Hi, sorry about that. I found it was a bug of oozie, and fix it by update oozie-4.1.0-cdh5.6.0 to oozie-4.1.0-cdh5.12.0.



在 2017年12月4日,下午2:33,钟老五 <zhong...@gmail.com> 写道:

My hue version is   4.0

and oozie server version is 


Romain Rigaux

unread,
Dec 4, 2017, 1:25:52 PM12/4/17
to 钟老五, via Hue-Users
Thanks for the info, indeed Oozie was improved since cdh 5.6 (very old), see if you can upgrade to CDH 5.13 :)

--
You received this message because you are subscribed to the Google Groups "Hue-Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hue-user+unsubscribe@cloudera.org.

Reply all
Reply to author
Forward
0 new messages