Open GoogleCodeExporter opened 8 years ago
I can take care of this one :) I have a good idea for it.
Original comment by genia.li...@gmail.com
on 9 Jun 2013 at 4:25
A question: right now the behavior is as follows:
1. I run a query that takes on average 10 seconds (I have a dataset I can load
for this).
2. While that is running, I run another query, e.g., an erroneous one such as
> foo = "1"
3. Output box displays an error.
4. Moments later, output box displays the output of the longer query.
Do we want to display the earlier one? Do we want to display the later one?
Should a new query override an existing query? I can implement any of these,
but I am not sure of what is the Asterix UI desired behavior for queries that
take a while and what should happen in between.
Original comment by genia.li...@gmail.com
on 9 Jun 2013 at 8:59
This one is ready to be merged, and is relevant to #526
https://code.google.com/p/asterixdb/issues/detail?id=526
In particular, it fixes the UI side of canceling, but not the backend side of
it.
Original comment by genia.li...@gmail.com
on 23 Jun 2013 at 7:05
Does this mean that the long running job, which needed to be canceled,
would still be running as a Hyracks job even after the Cancel button is
clicked on the Web UI front end ?
Original comment by khfaraaz82
on 24 Jun 2013 at 6:27
Original issue reported on code.google.com by
khfaraaz82
on 8 Jun 2013 at 9:51