Hi All,
Let me provide a bit more background on our thinking for pricing for the
Search API. We use the experimental phase for many APIs to test the API's
stability, get developer feedback and to fine-tune our pricing. It's
important to us that we only publish pricing when we are confident that
I guess what I'm most interested in is knowing how it will compare,
pricewise and performancewise, to using the datastore for FTS.
Obviously the datastore doesn't provide all the bells and whistles,
but it's pretty easy to store all the fragments of a set of words in
an indexed list property. For
On Fri, May 11, 2012 at 4:17 PM, Adam Sah adam@gmail.com wrote:
- this is pre-release, and if you personally can't bear that risk, then let
others play beta-tester for you.
- if Google waits for pricing before release then that delays the release,
which nobody wants.
- pricing can
(GAE team: congrats!!! on search-- please add clustered/grouped
resultshttp://wiki.apache.org/solr/FieldCollapsingto your todo list-- it's
very hard to emulate such a feature at the app
layer)
Jeff:
- this is pre-release, and if you personally can't bear that risk, then
let others play
Congratulations!
Would you be able to share an estimate on when the Search API will be
available from the Go runtime? I understand that both are experimental, but
is it actively being worked on or is still on the todo list?
Thank you,
Kyle
--
You received this message because you are
hi Kyle,
It is on the list, but we can't comment on any dates for it.
On 11 May 2012 11:07, Kyle Finley kylefin...@gmail.com wrote:
Congratulations!
Would you be able to share an estimate on when the Search API will be
available from the Go runtime? I understand that both are experimental,
On Tue, May 8, 2012 at 7:49 PM, Ugorji ugo...@gmail.com wrote:
If I sink in development time using it, and build my application to depend
on it, and then the price is released and it's prohibitive to me, I've lost
a fair amount of development time.
I concur. It's not necessary to have a
It will be nice if we had an idea of the price before committing to using
it. We've been down this road before and it left a bad taste when the
pricing was announced.
On Tuesday, May 8, 2012 5:54:04 PM UTC-4, Christina Ilvento wrote:
Hi All,
As you may have noticed on our
On Tue, May 8, 2012 at 11:03 PM, Ugorji wrote:
It will be nice if we had an idea of the price before committing to using
it.
Surely the idea is you don't commit to using it until it graduates
from experimental.
The free quota is there to experiment (and help Google figure out how
much it
I think features have been released before but we knew the price
(TaskQueues, etc). The feature is out of trusted testers mode (after many
many months). It's now in experimental but generally available mode, which
tells me that the API's may change somewhat but the feature is here to
stay.
based on existing pricing model - imho its price will be high.
more indexes + more datastore (storage, read, write, ...) + more
instances needed + ...
On May 9, 7:49 am, Ugorji ugo...@gmail.com wrote:
I think features have been released before but we knew the price
(TaskQueues, etc). The
11 matches
Mail list logo
