Revision history of "(7429.31052017.113000182) BIGDATA4GEO" (Q2064479)

Jump to navigation Jump to search

Diff selection: Mark the radio buttons of the revisions to compare and hit enter or the button at the bottom.
Legend: (cur) = difference with latest revision, (prev) = difference with preceding revision, m = minor edit.

8 April 2023

5 July 2022

  • curprev 14:0314:03, 5 July 2022DG Regio talk contribs 56,654 bytes +37,542 Changed label, description and/or aliases in da, el, hr, ro, sk, mt, pt, fi, pl, sl, cs, lt, lv, bg, hu, ga, sv, et, nl, fr, de, es, and other parts: Adding translations: da, el, hr, ro, sk, mt, pt, fi, pl, sl, cs, lt, lv, bg, hu, ga, sv, et,

15 June 2022

4 February 2022

25 January 2022

24 December 2021

23 December 2021

16 December 2021

2 November 2020

17 July 2020

9 June 2020

24 March 2020

23 March 2020

  • curprev 13:5713:57, 23 March 2020DG Regio talk contribs 10,169 bytes +1,284 Created claim: summary (P836): AT THE HEART OF THE PROPOSAL BIGATA4GEO C?? VOLONT? IN YOUR OPINION, TO EXPAND ITS TENDER WITH SOLUTIONS ADAPTED TO THE NEEDS OF SCALABILITEN? AND SPEED UP? TYPICAL OF THE BIG DATA PARADIGM. BIG DATA? A TERM WHICH REFERS TO A COLLECTION OF DATA, EVEN HETEROGENEOUS ONES, COS? BIG AND COMPLEX TO BE INADEQUATE FOR HARDWARE AND SOFTWARE SOLUTIONS USED FOR THE MANAGEMENT AND PROCESSING OF TRADITIONAL DATABASES. THE CRITICAL PHASES THAT NEED TO BE ADD...

18 March 2020

12 March 2020

7 March 2020