Demo Data from SIGIR 2026 / reviewers in the wild / expert
Vivek Sawant
dblp:88/464
· DBLP profile ↗
1ranked-venue papers
1as first author
0since 2021 · last 2005
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 1 · 1 first-author
Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.
| Computer architecture, parallel and distributed computing, and storage systems
1 paper |
Distributed systems · 100% |
Topics — the 2 heaviest of 2, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Distributed systems › peer-to-peer systems
lookup service |
0.1 | 1 | 2005 | Supporting arbitrary queries in peer-to-peer networks using hybrid routing · SOSP 2005 |
Distributed systems
peer-to-peer systems |
0.1 | 1 | 2005 | Supporting arbitrary queries in peer-to-peer networks using hybrid routing · SOSP 2005 |
Methods — techniques the papers use, named apart from their topics
key-based routing · 0.1attribute-partitioned indexing · 0.1
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2005 | Supporting arbitrary queries in peer-to-peer networks using hybrid routingabstractThe Peer-to-Peer (P2P) service model is being intensely explored for creating scalable and robust designs for decentralized Internet-scale applications. A lookup service for finding resources within a P2P network is one of the key services in the model. Lookup queries in P2P applications can be precise queries based on resource identifiers or imprecise ones involving keywords or attributes associated with resources. Some recent P2P designs have tried to leverage the efficient key-based routing mechanism of structured P2P systems for efficient lookups. These systems support precise queries directly and efficiently. To support imprecise queries, they create an index that maps keywords or attributes to keys used for structured routing and is attribute-partitioned across peers, that is, the index entry for a given attribute is stored at the peer addressed by its key. This approach has certain drawbacks. First, maintaining these index partitions in the presence of network churn is expensive. Second, popular keywords/attributes may get mapped to low capacity peers that cannot cope with the load. Third, the queries that require intersection of large indices to be computed, can be quite expensive to resolve. Vivek Sawant |
SOSP | 1 |