Query Bug

User avatar
Marco Grawunder
Posts: 272
Joined: Tue Jul 29, 2014 10:29 am
Location: Oldenburg, Germany
Contact:

Re: Query Bug

Post by Marco Grawunder » Thu Oct 16, 2014 1:36 pm

Fine. So no problems anymore?

flp
Posts: 51
Joined: Tue Sep 02, 2014 12:54 am

Re: Query Bug

Post by flp » Mon Oct 27, 2014 1:17 am

Unfortunately, there are probably still problems caused by the coalesce/join.

https://www.dropbox.com/sh/q8a269fq3437 ... Q9yka?dl=0

When I run the incommented part of the goal_counter query till the coalesce, I will receive exactly one value.
But when I join the result, I will get no more values, which is just crazy.

I tried several variants to exclude mistakes:

Code: Select all

First:
only_valid_goals = join({predicate = 'search_time + 6000000000000 >= timestamp'}, aggregating_ball_in_goal_data, only_balls)
Second:
test = join({predicate = 'goal_time <= start_interruption'}, aggregating_ball_in_goal_data, System.interruptions)

and some other variants

User avatar
Marco Grawunder
Posts: 272
Joined: Tue Jul 29, 2014 10:29 am
Location: Oldenburg, Germany
Contact:

Re: Query Bug

Post by Marco Grawunder » Mon Oct 27, 2014 10:03 am

I am not sure if I get your problem right: As an output of the coalese operator you get one value and when you join in with other values you get multiple output?

This could be because of the temporal logic. Join merges every tuple is has received from one input port with all tuples from the other input port. If multiple values overlap in time (this value is read from metadata and not from the timestamp attribute!) and the predicate is true, this leads to multiple output elements.

Could you give the values you exspect and the values you get?

flp
Posts: 51
Joined: Tue Sep 02, 2014 12:54 am

Re: Query Bug

Post by flp » Mon Oct 27, 2014 1:06 pm

No, I get one value form the coalesce, but I don't get any values back from the join and I expect some.

User avatar
Marco Grawunder
Posts: 272
Joined: Tue Jul 29, 2014 10:29 am
Location: Oldenburg, Germany
Contact:

Re: Query Bug

Post by Marco Grawunder » Mon Oct 27, 2014 1:55 pm

Are you sure that the input values of the join have overlapping time intervals? Double click on the query in the query view and right click on one operator to see its output

flp
Posts: 51
Joined: Tue Sep 02, 2014 12:54 am

Re: Query Bug

Post by flp » Mon Oct 27, 2014 6:56 pm

Just verified this now again.

I have uploaded pictures of my results.

I used the following query to verify the join parameters:

Code: Select all

joinout = ENRICH({minimumSize = 42, PREDICATE = RelationalPredicate('sensorid = sid')},System.metadata, soccergame)

only_balls = SELECT({predicate = 'entity = "Ball"'}, joinout)

playtime = SELECT({predicate = 'timestamp > 11178079936779303 && timestamp < 11178079936779303 + 6000000000000'}, only_balls)
Attachments
join_parameter.JPG
join_parameter.JPG (113.97 KiB) Viewed 734 times
join_result.JPG
join_result.JPG (39.37 KiB) Viewed 734 times
coalesce_result.JPG
coalesce_result.JPG (27.49 KiB) Viewed 734 times

User avatar
Marco Grawunder
Posts: 272
Joined: Tue Jul 29, 2014 10:29 am
Location: Oldenburg, Germany
Contact:

Re: Query Bug

Post by Marco Grawunder » Mon Oct 27, 2014 8:02 pm

I see the problem. The coalesce operator has no metadata...

Found the problem and fixed it. Will be on the update site tomorrow.

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest