Another thing is,
Let's say that we already have a structure data, the way we load that to
HDFS is to turn that one into a files ?
Cheers
On Sun, Oct 23, 2016 at 6:18 PM, Welly Tambunan wrote:
> So basically you will store that files to HDFS and use Spark to process it
> ?
>
&g
a isn't suited for, then HDFS / HBase may be better.
>
>
>
> We have files in which one line contains 500 fields (separated by pipe)
> and each of this fields is particularly important.
>
> Cassandra will not manage that since you will need 500 indexes. HDFS is
> the
then Cassandra should work for you. It is easier
to setup and do dev ops with, in my experience.
>
> On Sun, Oct 23, 2016 at 2:05 PM, Welly Tambunan wrote:
>>
>> I mean. HDFS and HBase.
>>
>> On Sun, Oct 23, 2016 at 4:00 PM, Ali Akhtar wrote:
>>>
&g
I mean. HDFS and HBase.
On Sun, Oct 23, 2016 at 4:00 PM, Ali Akhtar wrote:
> By Hadoop do you mean HDFS?
>
>
>
> On Sun, Oct 23, 2016 at 1:56 PM, Welly Tambunan wrote:
>
>> Hi All,
>>
>> I read the following comparison between hadoop and cassandra. Seems
rule them all ?
What we are trying to achieve is to minimize the moving part on our system.
Any response would be really appreciated.
Cheers
--
Welly Tambunan
Triplelands
http://weltam.wordpress.com
http://www.triplelands.com <http://www.triplelands.com/blog/>
