URI comes in pretty handy ;
video://videoprovider:codecSomething:myConverter:videoId
Or XRI but what Michael said.
> On Nov 14, 2016, at 11:59 AM, Michael Shuler wrote:
>
> Forward thinking, I would also suggest not storing the full URL, just
> the video ID of some sort. The application cod
Kevin,
We are about to release 2.0 of https://github.com/savoirtech/hecate
It is an ASL licensed library that started with Jeff Genender writing a Pojo
library in Hector for a project we did for Ecuador (Essentially all of Ecuador
uses this).
I extended this with Pojo Graph stuff like Collection
;> Whatever you do, make sure the driver you use supports CQL 3 and the native
>>> protocol. Thrift, like BOP, will most likely go away at some point in the
>>> future.
>>
>> Read what Johan stated… “hecate-cql3” <— CQL 3
>>
>> I think a nice
e community...
>>
>>
>>
>>> Whatever you do, make sure the driver you use supports CQL 3 and the native
>>> protocol. Thrift, like BOP, will most likely go away at some point in the
>>> future.
>>
>> Read what Johan stated… “hecate-cql3”
Cassandra-unit 2.0X works awesomely,
if you are willing to spend the slightly few more cycles, - Look at farsandra.
:)
I copied Farsandra (since there was no release) into hecate.
On Jun 11, 2014, at 11:02 PM, Kevin Burton wrote:
> Maybe this is an anti-pattern.. please feel free to flame me
We treat this on an Object level in Java as a new table with separate Hydration.
On a Map level we currently utilize an Internal CQL3 map where we replace the
non scalar values with
separate tables - we just stick the ID in.
Same for Sets, Arrays and such.
You get more writes but you also have
Well to throw fire on the debate, that was actually really simple in Thrift.
On Jun 13, 2014, at 10:50 PM, Kevin Burton wrote:
> I could see just saying screw it and storing a serialized json object that
> gets read back in automatically as a map. That wouldn't be too painful but
> just not s
I think you are going to be creating problems that the drivers were designed
to avoid, it is not a good idea in general.
/je
On Jun 27, 2014, at 11:28 AM, Serge Fonville wrote:
> Hector is same way, if any node is slow to responds, times out or dies hector
> will remove it from the pool leavin
