Pith. sign in

REVIEW 3 major objections 5 minor 64 references

Advancing Polyglot Big Data Processing using the Hadoop ecosystem

T0 review · 3 major / 5 minor · reviewed 2026-08-16 · deepseek-v4-flash

Challenge this review Re-run · record.json Download PDF Read on arXiv ↗ Review JSON

Pith's one-line read The Hadoop ecosystem can serve as a polyglot big data platform, pairing each data type with the right store and engine.

desk verdict A competent but unoriginal survey of Hadoop components that promises a monoglot comparison it never delivers, and asserts a polyglot efficiency claim without testing it. read the letter →

arxiv 2504.14322 v1 pith:U3FUFQHU submitted 2025-04-19 cs.DC

Antony Seabra , Sergio Lifschitz This is my paper · ORCID
classification cs.DC
keywords polyglotpersistencedataprocessingHadoopecosystemHDFSbiglakesreal-timeanalyticsNoSQLstores
verification ladder T0 review T1 audit T2 compute T3 formal

The pith

A machine-rendered reading of the paper's core claim, the machinery that carries it, and where it could break.

The reading

The paper sets out to establish that the Hadoop ecosystem, with HDFS at its center, can serve as a polyglot big data processing platform: one where different storage systems and processing engines are chosen for each data type and task. It argues that mixing polyglot persistence (HBase for real-time read/write, Hive for warehouse queries, external tables over raw files) with polyglot computing (MapReduce, Spark, Storm/Kafka streaming, SQL engines) yields efficient and scalable processing, and it illustrates the combination through healthcare, stock market, social network, and smart city scenarios. The paper's evidence is architectural: it assembles the ecosystem's components, explains each one's role, and maps them to workload needs. A sympathetic reader would take the claim as a design thesis: a single HDFS-centered platform can replace several specialized monoglot systems, but measurement of that advantage is left to future work.

What carries the argument

The mechanism that carries the argument is a four-phase workflow centered on HDFS: an Ingestion Phase that lands raw data in a Landing Zone, a transformation step that produces an Enriched Zone, a Storage Phase that routes data to Hive internal tables, Hive external tables, or HBase tables, and a processing phase where distinct tasks read from the stores best matched to their needs. The load-bearing design pattern is HDFS as a shared raw-data repository combined with per-task engine and store selection, supported by integration points such as Hive external tables (a schema over shared files), Hive-HBase integration, and mediator systems like Apache Calcite that expose one SQL interface over heterogeneous stores.

What would settle it

Run the same workload twice on one cluster: once with a polyglot stack (for example, Kafka for ingestion, HBase for live reads, Hive for warehousing, and Spark MLlib for modeling) and once with a single monoglot alternative (for example, Spark alone reading from HDFS), using identical data, queries, and hardware, then measure end-to-end latency, throughput, and resource use. If the monoglot configuration matches or beats the polyglot one on the metrics the paper cites, the central practical claim is not supported.

Watch

Extended reading notes

Core claim

Polyglot Big Data Processing is the paper's central concept: using various data stores and processing technologies suited to different data types within one platform. The specific claim is that the Hadoop ecosystem, centered on HDFS, already contains the building blocks for this: HDFS as common storage; YARN for resource management; MapReduce and Spark for batch and in-memory processing; Hive, Impala, and Presto as SQL engines; HBase, Cassandra, Neo4j, MongoDB, and others as specialized stores; Kafka, Storm, Flume, and NiFi for ingestion and streaming; and Calcite-like mediators for unified query access. Arranged well, these components let each task read from the most appropriate store and process with the most appropriate engine, enabling efficient and scalable data processing and real-time analytics.

Load-bearing premise

The claim rests on the assumption that the proposed component combinations, such as Kafka ingestion plus HBase storage plus Hive warehousing plus Spark MLlib, actually deliver the promised efficiency, scalability, and real-time benefits in real deployments.

Editorial extensions

If this is right

  • If the claim is correct, a single HDFS-centered data lake can host both batch and streaming workloads, replacing separate monoglot clusters for warehousing, real-time access, and machine learning.
  • Organizations can route data by type: HBase for low-latency key access, Hive external tables for SQL over raw files, Hive internal tables for managed warehouse data, and Spark or MapReduce for heavy computation.
  • Domains with mixed data velocity, such as healthcare monitoring and smart cities, can keep all their data in one platform and still get real-time alerts alongside historical analytics.
  • The polyglot approach defines a comparison agenda: which component pairs perform best, and where polystore mediators are needed, which the paper explicitly names as future work.

Reading between the lines

Editorial extensions of the paper, not claims the author makes directly.

  • Editorial inference: if the thesis holds, the practical adoption path is incremental—teams can add specialized stores and engines around an existing HDFS data lake rather than replacing their stack, which lowers the barrier to polyglot processing.
  • Editorial inference: the claimed advantage likely depends on workload heterogeneity; a monoglot system may remain competitive for uniform workloads, so the strongest test cases are mixed-velocity, mixed-model datasets.
  • Editorial inference: a concrete next experiment suggested by the paper would be a benchmark comparing mediator-based querying (for example, Calcite across Hive, MongoDB, and HBase) against hand-written federation logic, measuring query latency and development effort.
  • Editorial inference: the architecture also implies operational costs, because many components must run in one cluster, so a fair comparison should include administration overhead and not only query speed.
Share X Bluesky LinkedIn Reddit HN

Signed reviews

No signed human review yet.

Editorial analysis

A structured set of objections, weighed in public.

Desk editor's note, referee report, and a circularity audit.

Referee Report

3 major / 5 minor

Summary. The paper argues that the Hadoop ecosystem, centered on HDFS, can serve as a polyglot big data processing platform in which different storage systems (HBase, Hive, Cassandra, etc.) and processing engines (MapReduce, Spark, Storm, Kafka) are selected per workload. It reviews the ecosystem's storage, resource management, processing, programming, SQL, and NoSQL components; discusses polyglot persistence and its relationship to the CAP theorem; proposes a general polyglot architecture with ingestion, storage, and processing phases; and illustrates the approach with four hypothetical use cases (healthcare, stock market, social networks, smart cities). The paper concludes that the approach enables efficient and scalable processing and lists benchmarking and comparative studies as future work.

Significance. If the manuscript's empirical claims were substantiated, the paper would offer a useful synthesis of how Hadoop ecosystem components can be orchestrated as a polyglot platform, and the use cases would be a helpful orientation for practitioners. The manuscript is clearly written, covers a broad set of technologies, and provides instructive diagrams. Its strength is conceptual: the claim that HDFS can act as a central repository with multiple processing engines and storage systems is defensible from the cited documentation. However, the paper does not yet support the stronger claim of efficiency and scalability advantages over monoglot systems, and the comparative analysis promised in the introduction is absent. The contribution is currently at the level of a survey or position paper rather than an empirically validated research advance.

major comments (3)
  1. [Section 1 (Introduction)] The introduction promises "a comparative analysis of these polyglot strategies against traditional, or monoglot, systems," but the manuscript never delivers such a comparison. Sections 4 and 5 only describe the polyglot architecture and hypothetical use cases, and Section 7 explicitly lists "the comparative analysis of different polystores within the Hadoop ecosystem" as future work. This is a load-bearing gap because the title and abstract claim that the approach "advances" polyglot big data processing beyond conventional monoglot systems.
  2. [Sections 5.1-5.4] The use cases are presented as illustrations ("Consider...", "Imagine...") and contain no implementation, dataset, or measured benchmark. The central assertion in Section 4 that polyglot processing "allows for efficient and scalable data processing" is therefore unsupported by evidence in the manuscript. The conclusion (Section 7) concedes this when it lists "executing comprehensive tests across the various domains" as future work, so the paper's main practical claim is currently a hypothesis rather than an established result.
  3. [Section 5.3] The only reference to an evaluation in the use-case sections is the sentence "The evaluation of the jobs related to this use case can be found in [1]," which defers to a companion paper by the same authors. Because [1] is not included and its methodology and results are not summarized, readers cannot verify the claimed benefits for the social network scenario, and the manuscript is not self-contained.
minor comments (5)
  1. [Section 2.2] The acronym "Y ARN (Yet Another Resource Negotiator)" contains a typo; it should be "YARN", and the name is spelled inconsistently as "Yarn" elsewhere in the same section.
  2. [Section 2.3.1] The text says that Resilient Distributed Datasets "today they are called just Dataframes." RDDs and DataFrames are distinct abstractions in Spark; this conflation should be corrected.
  3. [Section 3.2] The CAP theorem discussion is generic and does not explain how the consistency-availability-partition trade-offs apply to the specific Hadoop components selected in the proposed architecture; consider tying it concretely to HBase, Hive, and Kafka.
  4. [Section 5] The section heading and opening sentence claim "real-world examples or case studies," but the scenarios that follow are hypothetical as written. The wording should be changed to "illustrative scenarios" unless actual deployments are described.
  5. [References] The reference list is inconsistent: some entries include access dates for URLs and others do not, and some entries (e.g., [36]) appear to have odd metadata. Please standardize citation formatting.

Circularity Check

0 steps flagged · score 0.0 of 10

No circularity: the paper is a survey/position piece with no derivation chain; unsupported efficiency claims are not circular.

full rationale

This paper is a survey/position paper with no formal derivation, equations, or fitted parameters, so there is no derivation chain that could reduce to its own inputs. The central claim in Section 4, that polyglot data processing in the Hadoop ecosystem 'allows for efficient and scalable data processing,' is an empirical assertion, not a derived result. Section 5's use cases are explicitly illustrative ('Consider...' and 'Imagine...'), and Section 7 defers 'executing comprehensive tests' and comparative polystore analysis to future work. That makes the efficiency/scalability claim unsupported by evidence presented in this paper, but unsupported is not the same as circular. The only self-citation is [1] in Section 5.3, which points to a companion paper for evaluation of the social network jobs; its results are not reproduced here, but the central polyglot claim does not depend on [1] for its definition or derivation. No parameter is fitted to a subset of data and renamed a prediction, no uniqueness theorem is imported from the authors' prior work, no ansatz is smuggled in via self-citation, and no known result is merely renamed. Therefore no circular step can be exhibited, and the appropriate finding is no significant circularity, score 0.

Assumptions & free parameters 0 free parameters · 3 assumptions · 0 invented entities

The paper introduces no free parameters and no invented entities. Its central claim rests on three assumptions: that Hadoop components behave as documented, that a data lake can function as a polystore-like platform, and that the hypothetical use case architectures would actually deliver their asserted benefits. The latter is explicitly deferred to future work in the conclusions.

assumptions (3)
  • domain assumption The Hadoop ecosystem components behave as described in their documentation and cited references (e.g., HDFS replication, Spark in-memory processing).
    The paper accepts vendor and documentation claims about components, e.g., Sections 2.1-2.3, without independent verification.
  • domain assumption Data lakes with raw data in HDFS can function in a polystore-like manner and benefit from polyglot persistence.
    Section 4 asserts this, but no benchmark or implementation demonstrates it.
  • ad hoc to paper The described use cases (Sections 5.1-5.4) represent feasible and beneficial applications.
    These are hypothetical architectures with no evaluation; the claimed benefits are asserted.

how reviews work

0 comments
Cite this review

Pith. "Pith review of Advancing Polyglot Big Data Processing using the Hadoop ecosystem." pith.science (2026). https://pith.science/paper/U3FUFQHU

@misc{pith2026250414322,
  author       = {Pith},
  title        = {Pith review of: Advancing Polyglot Big Data Processing using the Hadoop ecosystem},
  year         = {2026},
  howpublished = {\url{https://pith.science/paper/U3FUFQHU}},
  note         = {Machine review of arXiv:2504.14322}
}
read the original abstract

This article explores the utilization of the Hadoop ecosystem as a polyglot big data processing platform, focusing on the integration of diverse computation and storage technologies and their potential advantages in certain computational contexts. It delves into the potential of this ecosystem as a unified platform highlighting its architectural foundations and their complementary strengths in distributed storage, processing efficiency and real-time analytics. The article explores potential use cases within domains such as Smart Cities and Social Networks, illustrating how the platform's diverse components can be orchestrated in a polyglot manner and how these fields can benefit from the ecosystem's capabilities. Finally, the article concludes by showcasing alternatives for future research, including specialized architectural aspects of the ecosystem to advance the polyglot paradigm.

Figures

Figures reproduced from arXiv: 2504.14322 by the authors.

Figure 1
Figure 1. Hadoop ecosystem In addition, Hadoop’s open-source nature allowed for widespread adoption, lead￾ing to a vibrant and active community of developers contributing to its ongoing devel￾opment and evolution. The Apache Software Foundation, which stewards the Hadoop project, plays a pivotal role in coordinating the development efforts and ensuring that Hadoop remains a high-quality, reliable framework for big data proces… view at source ↗
Figure 2
Figure 2. HDFS architecture [23] Further enhancing this replication scheme is HDFS’s rack-awareness feature, an intelligent data placement strategy that extends beyond mere node-level redundancy. Rack￾awareness considers the physical configuration of the cluster, ensuring that data replicas are not only distributed across different nodes but also across different racks. This spatial dispersion of data helps mitigate the risk … view at source ↗
Figure 3
Figure 3. Distributed Processing with MapReduce [60] As illustrated in figure 3, the input comprises three lines which are partitioned into three parts during the Splitting phase and forwarded to individual Map-type tasks. During the Mapping phase, each Map task operates on its respective input on a cluster node and generates a key-value structure. In the specific example, the Map task returns the word count. Subsequently, in… view at source ↗
Figures from the paper (8 more)
Figure 4
Figure 4. Figure 4: Apache Spark Resilient Distributed Datasets [PITH_FULL_IMAGE:figures/full_fig_p007_4.png]
Figure 5
Figure 5. Figure 5: Apache Hive internal and external tables [PITH_FULL_IMAGE:figures/full_fig_p008_5.png]
Figure 6
Figure 6. Figure 6: Polyglot persistence in E-commerce application [PITH_FULL_IMAGE:figures/full_fig_p011_6.png]
Figure 7
Figure 7. Figure 7: Polyglot Architecture workflow, Tasks 1, 2 and 3 each represent specific analytical or processing jobs within the platform. The data store chosen for each task is based on its compatibility with the task’s requirements. Task 1 might interact directly with an enriched J…
Figure 8
Figure 8. Figure 8: Healthcare Polyglot Data Processing As a complement, the solution may leverage Spark’s MLlib for machine learn￾ing tasks, such as predicting patient readmission risks or identifying potential outbreaks of hospital-acquired infections. By training models on historical d…
Figure 9
Figure 9. Figure 9: Stock Market Polyglot Data Processing Further, harness Spark’s MLlib to develop and train machine learning models that predict stock price movements, discern market trends and evaluate risks by analyzing his￾torical and real-time data, offering predictive insights to i…
Figure 10
Figure 10. Figure 10: Social Networks Polyglot Data Processing [PITH_FULL_IMAGE:figures/full_fig_p018_10.png]
Figure 11
Figure 11. Figure 11: Smart Cities Polyglot Data Processing Hadoop ecosystem is an emerging area that addresses the complexities and challenges of managing diverse data types in large-scale environments and harnessing the power of multiple programming languages, computational paradigms, fr…

Discussion (0). Continue with ORCID to comment.

Reference graph

Works this paper leans on

64 extracted references · 63 canonical work pages

  1. [1]

    Seabra, S

    A. Seabra, S. Lifschitz. Towards Polyglot Data Processing in Social Networks using the Hadoop-Spark Ecosystem. In: CS & IT Conference Proceedings, v. 15, n. 1, 2025

    work page 2025

  2. [2]

    Aghayev, S

    A. Aghayev, S. Weil, M. Kuchnik, M. Nelson, G. R. Ganger, G. Amvrosiadis. File systems unfit as distributed storage backends: lessons from 10 years of Ceph evolution. In: Proceedings of the 27th ACM Symposium on Operating Systems Principles, p. 353- 369, 2019

    work page 2019

  3. [3]

    Al Nuaimi, H

    E. Al Nuaimi, H. Al Neyadi, N. Mohamed, J. Al-Jaroodi. Applications of big data to smart cities. Journal of Internet Services and Applications, v. 6, p. 1-15, 2015

    work page 2015

  4. [4]

    Al-Mekhlal, A

    M. Al-Mekhlal, A. A. Khwaja. A synthesis of big data definition and characteristics. In: 2019 IEEE International Conference on Computational Science and Engineering (CSE) and IEEE International Conference on Embedded and Ubiquitous Computing (EUC), p. 314-322, 2019

    work page 2019

  5. [5]

    K. Aziz, D. Zaidouni, M. Bellafkih. Real-time data analysis using Spark and Hadoop. In: 2018 4th International Conference on Optimization and Applications (ICOA), p. 1-6, 2018

    work page 2018

  6. [6]

    Boranbayev, G

    A. Boranbayev, G. Shuitenov, S. Boranbayev. The method of data analysis from social net- works using Apache Hadoop. In: Information Technology-New Generations: 14th International Conference on Information Technology, p. 281-288, 2018

    work page 2018

  7. [7]

    Borthakur, J

    D. Borthakur, J. Gray, J. S. Sarma, K. Muthukkaruppan, N. Spiegelberg, H. Kuang, K. Ranganathan, D. Molkov, A. Menon, S. Rash et al. Apache Hadoop goes realtime at Facebook. In: Proceedings of the 2011 ACM SIGMOD International Conference on Management of Data, p. 1071-1080, 2011

    work page 2011

  8. [8]

    Apache Calcite

    Apache Calcite. Apache Calcite. [Online]. Available: https://calcite.apache. org/. Accessed: 2024-03-27, 2024

    work page 2024

Show all 64 references
  1. [9]

    Cassandra

    Cassandra. Cassandra. [Online]. Available: https://cassandra.apache.org/ doc/latest/cassandra/developing/data-modeling/intro. html. Accessed: 2024-03-27, 2024

    2024

  2. [10]

    Chakraborty, S

    K. Chakraborty, S. Bhattacharyya, R. Bag. A survey of sentiment analysis from social media data. IEEE Transactions on Computational Social Systems, v. 7, n. 2, p. 450- 464, 2020

    2020

  3. [11]

    Conejero, P

    J. Conejero, P. Burnap, O. Rana, J. Morgan. Scaling archived social media data analysis using a Hadoop cloud. In: 2013 IEEE Sixth International Conference on Cloud Computing, p. 685-692, 2013

    2013

  4. [12]

    Cunha, C

    J. Cunha, C. Silva, M. Antunes. Health Twitter big data management with Hadoop frame- work. Procedia Computer Science, v. 64, p. 425-431, 2015

    2015

  5. [13]

    Davies, A

    A. Davies, A. Orsaria. Scale out with GlusterFS. Linux Journal, v. 2013, n. 235, p. 1, 2013

    2013

  6. [14]

    J. Dean, S. Ghemawat. MapReduce: Simplified data processing on large clusters, 2004

    2004

  7. [15]

    Demirbaga

    U. Demirbaga. HTwitt: a Hadoop-based platform for analysis and visualization of stream- ing Twitter data. Neural Computing and Applications, v. 35, n. 33, p. 23893-23908, 2023

    2023

  8. [16]

    Elmasri, S

    R. Elmasri, S. B. Navathe. Fundamentals of Database Systems 7th ed., 2016

    2016

  9. [17]

    K. Garg, D. Kaur. Sentiment analysis on Twitter data using Apache Hadoop and perfor- mance evaluation on Hadoop MapReduce and Apache Spark. In: Proceedings on the International Conference on Artificial Intelligence (ICAI), p. 233-238, 2019

    2019

  10. [18]

    N. A. Ghani, S. Hamid, I. A. T. Hashem, E. Ahmed. Social media big data analytics: A survey. Computers in Human Behavior, v. 101, p. 417-428, 2019

    2019

  11. [19]

    Ghemawat, H

    S. Ghemawat, H. Gobioff, S.-T. Leung. The Google file system. In: Proceedings of the nineteenth ACM symposium on Operating systems principles, p. 29-43, 2003

    2003

  12. [20]

    Glake, F

    D. Glake, F. Kiehn, M. Schmidt, F. Panse, N. Ritter. Towards Polyglot Data Stores- Overview and Open Research Questions. arXiv preprint arXiv:2204.05779, 2022

    2022 arXiv

  13. [21]

    HBase. HBase. [Online]. Available: https://hbase.apache.org/. Accessed: 2024-03-27, 2024

    2024

  14. [22]

    HBaseIntegration

    HBaseIntegration. HBaseIntegration. [Online]. Available: https://cwiki. apache.org/confluence/display/Hive/HBaseIntegration. Accessed: 2024-03-27, 2024

    2024

  15. [23]

    Understanding MapReduce with Hadoop

    Apache HDFS. Understanding MapReduce with Hadoop. [Online]. Available: https://hadoop.apache.org/docs/r1.2.1/hdfs_design.html# Data+Replication. Accessed: 2024-01-20, 2024

    2024

  16. [24]

    Hindman, A

    B. Hindman, A. Konwinski, M. Zaharia, A. Ghodsi, A. D. Joseph, R. Katz, S. Shenker, I. Stoica. Mesos: A platform for Fine-Grained resource sharing in the data center. In: 8th USENIX Symposium on Networked Systems Design and Implementation (NSDI 11), 2011

    2011

  17. [25]

    A. Holmes. Hadoop in practice, 2014

    2014

  18. [26]

    Hupfeld, T

    F. Hupfeld, T. Cortes, B. Kolbeck, J. Stender, E. Focht, M. Hess, J. Malo, J. Marti, E. Cesario. The XtreemFS architecture-a case for object-based file systems in Grids. Concurrency and computation: Practice and experience, v. 20, n. 17, p. 2049-2060, 2008

    2008

  19. [27]

    Jenhani, M

    F. Jenhani, M. S. Gouider, L. B. Said. Streaming social media data analysis for events ex- traction and warehousing using Hadoop and Storm: Drug abuse case study. Procedia Computer Science, v. 159, p. 1459-1467, 2019

    2019

  20. [28]

    A. K. Karun, K. Chitharanjan. A review on Hadoop HDFS infrastructure extensions. In: 2013 IEEE Conference on Information & Communication Technologies, p. 132-137, 2013

    2013

  21. [29]

    P. P. Khine, Z. Wang. A review of polyglot persistence in the big data world. Information, v. 10, n. 4, p. 141, 2019

    2019

  22. [30]

    W. K. Lai, Y .-U. Chen, T.-Y . Wu, M. S. Obaidat. Towards a framework for large-scale multimedia data storage and processing on Hadoop platform. The Journal of Super- computing, v. 68, p. 488-507, 2014

    2014

  23. [31]

    Lajam, S

    O. Lajam, S. Mohammed. Revisiting Polyglot Persistence: From Principles to Practice. International Journal of Advanced Computer Science and Applications, v. 13, n. 5, 2022

    2022

  24. [32]

    J. Lin, A. Kolcz. Large-scale machine learning at Twitter. In: Proceedings of the 2012 ACM SIGMOD International Conference on Management of Data, p. 793-804, 2012

    2012

  25. [33]

    H. Li. Alluxio: A virtual distributed file system, 2018

    2018

  26. [34]

    Hive LLAP

    Hive LLAP. Hive LLAP. [Online]. Available: https://cwiki.apache.org/ confluence/display/hive/llap. Accessed: 2024-03-27, 2024

    2024

  27. [35]

    Madaan, V

    A. Madaan, V . Sharma, P. Pahwa, P. Das, C. Sharma. Hadoop: solution to unstructured data handling. In: Big Data Analytics: Proceedings of CSI 2015, p. 47-54, 2018

    2015

  28. [36]

    Understanding MapReduce with Hadoop

    Apache MapReduce. Understanding MapReduce with Hadoop. [Online]. Avail- able: https://cwiki.apache.org/confluence/download/ attachments/120729986/MapReduce-SPA2008.pdf?version= 1&modificationDate=1562667747000&api=v2. Accessed: 2024-01-20, 2004

    2024

  29. [37]

    J. L. J. Marquez, I. G. Carrasco, J. L. L. Cuadrado. Challenges and opportunities in analytic-predictive environments of big data and natural language processing for social network rating systems. IEEE Latin America Transactions, v. 16, n. 2, p. 592- 597, 2018

    2018

  30. [38]

    Polyglot Persistence

    Martin Fowler. Polyglot Persistence. [Online]. Available: https://martinfowler. com/bliki/PolyglotPersistence.html. Accessed: 2024-03-27, 2011

    2024

  31. [39]

    Mesos Architecture

    Apache Mesos. Mesos Architecture. [Online]. Available: https://mesos.apache. org/documentation/latest/architecture/. Accessed: 2024-03-27, 2024

    2024

  32. [40]

    Nandimath, E

    J. Nandimath, E. Banerjee, A. Patil, P. Kakade, S. Vaidya, D. Chaturvedi. Big data anal- ysis using Apache Hadoop. In: 2013 IEEE 14th International Conference on Infor- mation Reuse & Integration (IRI), p. 700-703, 2013

    2013

  33. [41]

    Podhoranyi, L

    M. Podhoranyi, L. V ojacek. Social media data processing infrastructure by using Apache Spark big data platform: Twitter data analysis. In: Proceedings of the 2019 4th International Conference on Cloud Computing and Internet of Things, p. 1-6, 2019

    2019

  34. [42]

    Robinson, J

    I. Robinson, J. Webber, E. Eifrem. Graph databases: new opportunities for connected data, 2015

    2015

  35. [43]

    A. P. Rodrigues, N. N. Chiplunkar. Real-time Twitter data analysis using Hadoop ecosys- tem. Cogent Engineering, v. 5, n. 1, p. 1534519, 2018

    2018

  36. [44]

    M. A. Russell. Mining the social web: data mining Facebook, Twitter, LinkedIn, Google+, GitHub, and more, 2013

    2013

  37. [45]

    Sachdeva, J

    K. Sachdeva, J. S. Lamba, V . Sinha, N. Singh. Comparison of data processing tools in Hadoop. In: 2016 International Conference on Electrical, Electronics, Communica- tion, Computer and Optimization Techniques (ICEECCOT), p. 238-242, 2016

    2016

  38. [46]

    P. J. Sadalage, M. Fowler. NoSQL distilled: a brief guide to the emerging world of poly- glot persistence, 2013

    2013

  39. [47]

    Sarnovsky, P

    M. Sarnovsky, P. Butka, J. Paulina. Social-media data analysis using tessera framework in the Hadoop cluster environment. In: Information Systems Architecture and Tech- nology: Proceedings of 37th International Conference on Information Systems Ar- chitecture and Technology-IS...

    2016

  40. [48]

    Schaarschmidt, F

    M. Schaarschmidt, F. Gessert, N. Ritter. Towards automated polyglot persistence, 2015

    2015

  41. [49]

    Schwan et al

    P. Schwan et al. Lustre: Building a file system for 1000-node clusters. In: Proceedings of the 2003 Linux symposium, v. 2003, p. 380-386, 2003

    2003

  42. [50]

    ScyllaDB

    ScyllaDB. ScyllaDB. [Online]. Available: https://www.scylladb.com/. Ac- cessed: 2024-01-20, 2024

    2024

  43. [51]

    Sehgal, A

    D. Sehgal, A. K. Agarwal. Sentiment analysis of big data applications using Twitter Data with the help of HADOOP framework. In: 2016 International Conference System Modeling & Advancement in Research Trends (SMART), p. 251-255, 2016

    2016

  44. [52]

    Sethi, M

    R. Sethi, M. Traverso, D. Sundstrom, D. Phillips, W. Xie, Y . Sun, N. Yegitbasi, H. Jin, E. Hwang, N. Shingte et al. Presto: SQL on everything. In: 2019 IEEE 35th Interna- tional Conference on Data Engineering (ICDE), p. 1802-1813, 2019

    2019

  45. [53]

    S. Shaw, A. F. Vermeulen, A. Gupta, D. Kjerrumgaard, S. Shaw, A. F. Vermeulen, A. Gupta, D. Kjerrumgaard. Hive Tables DDL. Practical Hive: A Guide to Hadoop’s Data Warehouse System, p. 49-76, 2016

    2016

  46. [54]

    L. J. Sheela. A review of sentiment analysis in twitter data using Hadoop. International Journal of Database Theory and Application, v. 9, n. 1, p. 77-86, 2016

    2016

  47. [55]

    Apache Spark Resilient Distributed Datasets

    Spark. Apache Spark Resilient Distributed Datasets. [Online]. Available: https://www.tutorialspoint.com/apache_spark/apache_ spark_rdd.htm. Accessed: 2024-01-20, 2013

    2024

  48. [56]

    Srivastava, N

    K. Srivastava, N. Shekokar. A Polyglot Persistence approach for E-Commerce business model. In: 2016 International Conference on Information Science (ICIS), p. 7-11, 2016

    2016

  49. [57]

    Stieglitz, M

    S. Stieglitz, M. Mirbabaie, B. Ross, C. Neuberger. Social media analytics-Challenges in topic discovery, data collection, and data preparation. International journal of information management, v. 39, p. 156-168, 2018

    2018

  50. [58]

    Z. Tong. Elasticsearch: The Definitive Guide, 2015

    2015

  51. [59]

    M. N. V ora. Hadoop-HBase for large-scale data. In: Proceedings of 2011 International Conference on Computer Science and Network Technology, v. 1, p. 601-605, 2011

    2011

  52. [60]

    T. White. Hadoop: The definitive guide, 2012

    2012

  53. [61]

    D. Yang, H. Yang, P. Wang, S. Li. Design and Implement of Large-scale Social Network Analysis Platform Based on Hadoop. J. Inf. Hiding Multim. Signal Process., v. 8, n. 2, p. 300-309, 2017

    2017

  54. [62]

    Yarn Architecture

    Apache Yarn. Yarn Architecture. [Online]. Available: https://hadoop.apache. org/docs/stable/hadoop-yarn/hadoop-yarn-site/YARN.html. Accessed: 2024-03-27, 2024

    2024

  55. [63]

    Zafarani, M

    R. Zafarani, M. A. Abbasi, H. Liu. Social media mining: an introduction, 2014

    2014

  56. [64]

    Zaharia, M

    M. Zaharia, M. Chowdhury, T. Das, A. Dave, J. Ma, M. McCauly, M. J. Franklin, S. Shenker, I. Stoica. Resilient distributed datasets: A fault-tolerant abstraction for in- memory cluster computing. In: Presented as part of the 9th USENIX Symposium on Networked Systems Design and...

    2012

Pith tools

Reviewed August 16, 2026 · model on record in the stance chip above.