search

shamim8888 / asterixdb

Automatically exported from code.google.com/p/asterixdb
0 stars 0 forks source link

ADM/AQL 101 for closed types broken past 04b2b77a980767f3e57f5acf810953ab9df2bd39 #897

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
In master right now, the ADM/AQL 101 demo is broken for closed types. The 
reason behind this seems to be stale metadata. On the MD node, information on 
the name of nullable fields is computed, placed into the Datatype object, and 
inserted into the index. On the other side though, the caller also has a 
potentially stale version of this Datatype object without these names, but 
inserts it into their local MD cache anyway. 

The end result is that the RTree in the demo on sender-location from 
FacebookMessageType fails to be created, because the metadata record can't be 
created, due to the name of the field being null in the metadata cache. 

This doesn't happen in the test framework, likely due to the fact that 
everything is in one JVM. In that case, it seems that the object representing 
the datatype must be passed by reference through RMI, where in the case of 
separate JVMs, it is passed by value, so the changes aren't reflected on the 
caller's side.

Original issue reported on code.google.com by ima...@uci.edu on 9 Jun 2015 at 11:56

GoogleCodeExporter commented 8 years ago 
Fixed in 1445153fda37f0d244bb1648c27ac5df4c47a852, but more issues are being 
spawned from investigating the cause of this.

Original comment by ima...@uci.edu on 13 Jun 2015 at 1:45