So i'm using the timeseries tables, but I have more than one ID field - as i'm using 3 clustering columns in addition to the time field
I'll PR an example with support added, and no interface change, but there are a couple of considerations around the interface as it expects a single idField
which takes a single
id field as an interface, so its not easy to pass multiple fields in for equality. i'm thinking checking if the type passed through the interface is a map and using that?
FYI @crufter is away today, will be back tomorrow
Or change the API and switch to variadic arguments, not sure changing the existing API is a good idea though
Actually I guess creating a new function wouldnt change anything
Two approaches I see:
A philosophical, perhaps over engineered one
At the moment gocassa does not do a good job of encouraging people to create their own recipes because the existing ones are special (they can be acquired from the keyspace, if you add a recipe you have to change gocassa etc).
I definitely consider that as a design flow and this might be the best moment to fix it. Once this is fixed, people can write and reuse their own recipes without a modifying gocassa.
The already existing recipes can just serve as examples, to convey the idea, but nothing else.
A more punk rock, write it, merge it, forget it one
Title says it all: find an optimal interface and click merge.
So far the discussion resolves around the latter if I am not mistaken, I wonder what do you think about the former?
