search

ow2-proactive / scheduling-portal

http://try.activeeon.com
GNU Affero General Public License v3.0
4 stars 38 forks source link

Network Error appear when filtering job #512

Open MaelAudren opened 5 years ago

MaelAudren commented 5 years ago

image

mbenguig commented 5 years ago

It seems that applying a multiple-criteria filter generates a query concatenating all criteria under the same string. For example, filtering jobs with id=1 and id=52 (2 conditions) will generate the following query (without crash)

{ jobs( last:50 filter : [{ id : 152 status : PENDING },{ id : 152 status : RUNNING },{ id : 152 status : STALLED },{ id : 152 status : FINISHED },{ id : 152 status : PAUSED },{ id : 152 status : CANCELED },{ id : 152 status : FAILED },{ id : 152 status : KILLED },{ id : 152 status : IN_ERROR }] ){

Another example with priority = IDLE and priority = LOW will generate (with a quite similar exception, since IDLELOW is an unknown state)

{ jobs( last:50 filter : [{ priority : IDLELOW status : PENDING },{ priority : IDLELOW status : RUNNING },{ priority : IDLELOW status : STALLED },{ priority : IDLELOW status : FINISHED },{ priority : IDLELOW status : PAUSED },{ priority : IDLELOW status : CANCELED },{ priority : IDLELOW status : FAILED },{ priority : IDLELOW status : KILLED },{ priority : IDLELOW status : IN_ERROR }] ){

mboussaa commented 5 years ago

@mbenguig in another scenario, when you give a string value to an id, we hit the network error.