So you want to basically quiesce a dataset "all the way" - so that it's
not open at all, and perhaps so that the buffer pool also has none of
its pages resident?
On 4/12/17 2:26 PM, Ian Maxon wrote:
That's a little different than from what I'd like to do. Basically I
want to evict the dataset entirely. My alterior motive here is to test
the correctness of persisted storage artifacts as right now in many
cases this is not covered. It has been a recurring theme in many bugs
that there is some stored artifact on disk that is written incorrectly
but never read during tests, because often the tests simply never
encounter the path in which this would occur (restart,eviction, etc.)
On Wed, Apr 12, 2017 at 1:46 PM, Ildar Absalyamov
<[email protected]> wrote:
Ian,
There is an existing API, which does exactly that.
https://github.com/apache/asterixdb/blob/master/asterixdb/asterix-app/src/main/java/org/apache/asterix/api/http/server/ConnectorApiServlet.java#L123
<https://github.com/apache/asterixdb/blob/master/asterixdb/asterix-app/src/main/java/org/apache/asterix/api/http/server/ConnectorApiServlet.java#L123>
I have been successfully using it in my experiments.
On Apr 12, 2017, at 13:41, Ian Maxon <[email protected]> wrote:
Hey all,
I was working on a patch that would add a 'flush dataset' DDL command
(mainly for testing), and of course this would require adding 'flush'
as a new reserved word. What is the consensus on when this would be
permitted at this point? There are other ways to do this, of course, I
could expose this functionality through a separate API, and I am not
really partial to one solution or the other.
Thanks,
- Ian
Best regards,
Ildar
