Please use this identifier to cite or link to this item:
|Title:||On the complexity of view update analysis and its application to annotation propagation||Authors:||Cong, Gao
|Keywords:||DRNTU::Engineering::Computer science and engineering||Issue Date:||2012||Source:||Cong, G., Fan, W., Geerts, F., Li, J., & Luo, J. (2012). On the Complexity of View Update Analysis and Its Application to Annotation Propagation. IEEE Transactions on Knowledge and Data Engineering, 24(3), 506-519.||Series/Report no.:||IEEE transactions on knowledge and data engineering||Abstract:||This paper investigates three problems identified in  for annotation propagation, namely, the view side-effect, source side-effect, and annotation placement problems. Given annotations entered for a tuple or an attribute in a view, these problems ask what tuples or attributes in the source have to be annotated to produce the view annotations. As observed in , these problems are fundamental not only for data provenance but also for the management of view updates. For an annotation attached to a single existing tuple in a view, it has been shown that these problems are often intractable even for views defined in terms of simple SPJU queries . We revisit these problems by considering several dichotomies: (1) views defined in various subclasses of SPJU, versus SPJU views under a practical key preserving condition; (2) annotations attached to existing tuples in a view versus annotations on tuples to be inserted into the view; and (3) a single-tuple annotation versus a group of annotations. We provide a complete picture of intractability and tractability for the three problems in all these settings. We show that key preserving views often simplify the propagation analysis. Indeed, some problems become tractable for certain key preserving views, as opposed to the intractability of their counterparts that are not key preserving. However, group annotations often make the analysis harder. In addition, the problems have quite diverse complexity when annotations are attached to existing tuples in a view and when they are entered for tuples to be inserted into the view.||URI:||https://hdl.handle.net/10356/98880
|ISSN:||1041-4347||DOI:||10.1109/TKDE.2011.27||Rights:||© 2012 IEEE||Fulltext Permission:||none||Fulltext Availability:||No Fulltext|
|Appears in Collections:||SCSE Journal Articles|
Items in DR-NTU are protected by copyright, with all rights reserved, unless otherwise indicated.