The entire Hadoop ecosystem (including HDFS, Hive and HBase) is not designed for fast interactive/real time queries with less than few minutes responses. Instead Hadoop is well suited for batch programming (more than few minutes responses) with very big datasets (think about terabytes or petabytes).
If you just have a few Giga bytes dataset (wich is considered a small dataset in the Hadoop world) you better improve the performance of your queries remaining in the SQL world. For example if you are joining two or more tables you can denormalize your data so that you can avoid the join.
That said, there is an initiative called Stinger from Microsoft and Hortonworks which tries to improve the performance of Hive in order to make queries interactive. The introduced a tool called Tez which make Hive 10 to 100 times faster.
My suggestion would be to try the performance of hadoop by using a Hortonworks sandbox VM and test the performance of hive on your laptop. If you use the version 2.1, it comes already with Tez and the latest version of Hive.
You have to remember that with the Hortonworks sandbox you are using a cluster made of just one node. If you want improve the performance of the Hive query you can distribute your dataset and then the processing to more than one node.
Only with a real test with a sql database and hadoop you can see which solution is performing better. My guess would be that with such a small dataset and comparing your SQL database with Hive on just one node, you can still performs better with a SQL database. But with a bigger dataset and by using more that one node, the performance of the SQL database starts to degrade in favor of the hadoop solution.
P.S: I am a Hortonworks certified developer and instructor.