Get "Cannot remove index while it is open" after failed query

[GoogleCodeExporter]

Run the attached query on using the file 
https://www.dropbox.com/s/t4zic7i9ya781k1/0H_28_indexed.csv.
This will yield 

This can not be an instance of time [AlgebricksException]

Trying to run a modified version of the query after this yields:

Cannot remove index while it is open. [HyracksDataException]

Original issue reported on code.google.com by westm...@gmail.com on 9 Aug 2013 at 5:06

Attachments:

• query.aql

[GoogleCodeExporter]

Original comment by ima...@uci.edu on 14 Oct 2014 at 9:33

• Added labels: Weekly

[GoogleCodeExporter]

@Till, can you post the dataset file once again? The link is broken.

Original comment by ildar.absalyamov on 15 Oct 2014 at 4:12

[GoogleCodeExporter]

Unfortunately I cannot as I don't have the file anymore :(
Looking at the query it seems that the query and the data came from 
Informatics, but I'm not sure if they would still be able to reproduce what 
kind of file this was.

However, looking at the bug I think that the problem is that we get (got?) into 
a bad state when the CSV parser throws an exception. So you could 
- create a simple type with a time in it, 
- create some CSV data for that type with a broken time in it (maybe an empty 
field is enough as the type was non-optional in the example)
- try to load that CSV into a dataset using the type.

Hope this helps,
Till

Original comment by westm...@gmail.com on 15 Oct 2014 at 7:15

[GoogleCodeExporter]

OK, I was able to trigger time instance creation error, but not the "Cannot 
remove index while it is open"  exception.
After a failed insert simple selection (for $x in dataset return $x) from both 
HRM_28_raw\HRM_28 return the data. Is that the modified query, you were talking 
about?

Original comment by ildar.absalyamov on 15 Oct 2014 at 7:41

[GoogleCodeExporter]

I'm also guessing at this point, but another thing to try might be to insert a 
lot of data, such that we need more than just the in-memory component of the 
LSM tree. The fact that I put the file on dropbox could be an indicator that I 
was not able to trigger the problem with a smaller file that I could attach to 
the bug ...

Original comment by westm...@gmail.com on 15 Oct 2014 at 9:56

[GoogleCodeExporter]

After I fixed issue 803, this issue could be fixed as well. 
I couldn't check the test case reported in this issue due to the lack of the 
data file.
Please see issue 803.

Original comment by kiss...@gmail.com on 15 Oct 2014 at 10:40