Hi everyone I'm currently testing Hbase/Hadoop in terms of performance but also in terms off applicability. After some tries, and reads I'm wondering If Hbase is well fitted for the current need I'm testing.
Say I had logs on websites listing users going to webpage, reading an article, liking a piece of data, commenting or even bookmarking. I would store these logs on a long period and for a lot of different websites and I would like to use the data with these questions: - All users that have been to the webpage X in the last Ndays - All users that have liked and then bookmarked a page in a range of Y days. - All the pages that are commented X times in the last N days. - All users that have commented a page W and liked a page P. - All pages seen,liked or commented by a given user. As you see this might a very SQL way of thinking. The way I understand the questions being different in nature I would have different tables to answer them. Am I correct? How could this be represented and would sql be a better fit? The data would be large around a 10 Tbytes. regards
