MétaCan
Menu
Back to cohort
Record W2126420512

Experimental Validation as Support in the Migration from SQL Databases to NoSQL Databases

2015· article· en· W2126420512 on OpenAlex
Abraham Gomez, Rafik Ouanouki, Anderson Ravanello, Alain April, Alain Abran

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueInternational Conference on Cloud Computing · 2015
Typearticle
Languageen
FieldDecision Sciences
TopicScientific Computing and Data Management
Canadian institutionsUniversité du Québec à MontréalUniversité du QuébecÉcole de Technologie Supérieure
Fundersnot available
KeywordsNoSQLDatabaseComputer scienceSQLRelational databaseCloud computingCloud databaseProcess (computing)HeuristicBig dataData miningScalabilityArtificial intelligence
DOInot available

Abstract

fetched live from OpenAlex

NoSQL databases, also known Not only SQL databases, are a new type of databases that provides structures other than the tabular relations used in relational databases, for storage and retrieval data. This new databases are now a valuable asset to design complex real-time applications that use Big Data in cloud environments (NoSQL cloud databases). Today, the migration process from relational databases to NoSQL databases is unclear and mainly based on heuristic approaches such as the developers’ experience or intuitive judgments. This paper, which forms part of a more extensive research project regarding how the design and use of a guidelines set could improve the migration process. The results present an experiment designed to obtain a baseline that allows an effective comparison between two migration processes: the first one, without the use of any guidelines and based on the traditional heuristic approach and the second one, with the guidelines. The experiment reports that the use of such guidelines improves the migration process. KeywordsColumn oriented databases, NoSQL databases, distributed databases, software experimentation, cloud computing.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.004
metaresearch head score (Gemma)0.003
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesScholarly communication, Insufficient payload (model declined to judge)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.479
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0040.003
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0000.000
Scholarly communication0.0010.000
Open science0.0020.001
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0010.002

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.444
GPT teacher head0.480
Teacher spread0.036 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it