How to ask friendly Amazon Goddess Athena to get your partitioned data from Hadoop cluster Do you hesitate if you need a Hadoop cluster for a few Hive tables only ? Do you query your data not so frequently ? Do you want to save money on servers' maintenance and put your lazy data on the cloud ? Amazon thought about it and suggest you a serverless service: Amazon Athena. The short description on Amazon Athena web page give us a good point to start: An interactive query service

Dedicated to mongodump haters MongoDB 3.6 brought us a number of new improvements we can take now into consideration if it's more convenient, reliable and fast platform for NoSQL. A quick look into the website give us the most important add-ons to facilitate our work: Change streams enable you to create powerful data pipelines, moving data to wherever it’s needed using a time-ordered sequence of changes as they occur in the database. New causal consistency enforces strict, se

INTRODUCTION: In the last period we encounter a growing interest in MariaDB products (Galera Cluster, MaxScale for example) among our customers. Due to a number of projects related to this platform I would like to concentrate some prominent advantages of the platform and introduce a simple installation of Galera Cluster. Galera is a new kind of clustering engine which, unlike traditional MySQL master-slave replication, provides master-master replication and thus enables a new

Client’s requirements: The R&D team decided to delete an old non-relevant data of customers in order to decrease database size. The marketing department send this data in CSV format only therefore we need to load these accounts into MySQL temporary table for the future deletes based on this table. Solution: Python scripts that loads an original csv file, remove duplicated accounts and non-relevant columns, loads a new data into another csv file in order to save the previous o

Client’s requirements: Case #1: Stand-alone server with the old version 3.2.12 Case #2: Replica set with even number of servers (2) on the same geolocation (Holland) with an arbiter installed on Azure with the old versions 3.2.12. Servers hostnames (for demonstration only): nl1primary nl2secondary az1arbiter MongoDB stand-alone server’s upgrade (case #1) Download MongoDB Community server 64-bit (last version, at the time of writing it’s 3.4.4) as *.msi file to each server. On

Client’s requirements: Even number of servers (4) on two geolocations (UK and Holland) with a following priority - failover order from UK to Holland, arbiter should be installed on Azure. Servers hostnames (for demonstration only): uk1primary uk2secondary nl1secondary nl2secondary az1arbiter MongoDB servers’ installations Download MongoDB Community server 64-bit (last version, at the time of writing it’s 3.4.4) as *.msi file to each server. On each replica set member it’s rec