Getting more from the skyline operator through restricted skylines, regret minimizing sets and skyline ordering: a survey on their properties and comparison

March 26, 2022 ยท The Cartographer ยท ๐Ÿ› arXiv.org

๐Ÿ“š THE CARTOGRAPHER: The Cartographer
Survey/review paper โ€” maps the landscape rather than implementing a method.

"No code URL or promise found in abstract"
"Title-pattern auto-detect: Getting more from the skyline operator through restricted skylines, regret minimizing sets and skyli"

Evidence collected by the PWNC Scanner

Authors Claudio Migliorelli arXiv ID 2203.14086 Category cs.DB: Databases Cross-listed cs.IR Citations 0 Venue arXiv.org Last Checked 4 days ago
Abstract
Given a set of multidimensional points, the skyline operator returns a set of potentially interesting points from such a dataset. This popular operator filters out a set of tuples that are not dominated by other ones, reducing the size of a possibly large initial dataset. However, with the dataset dimensions growing, the query result of the skyline operator can have a high cardinality that could overwhelm the final user looking at the result, yielding the very opposite goal. Moreover, it doesn't allow any user to express their preferences over the attributes, in order to control the dataset cardinality and to return a more satisfying result. In this survey, we discuss and compare the more recent approaches developed to extend the skyline operator's functionalities, and we discuss their applicability in real-world scenarios. We show how these frameworks operate on the dataset and how they claim to mitigate the drawbacks coming from the skyline operator.
Community shame:
Not yet rated
Community Contributions

Found the code? Know the venue? Think something is wrong? Let us know!

๐Ÿ“œ Similar Papers

In the same crypt โ€” Databases