This is likely a common scenario and I'm wondering if someone has
already written some code to do this that I can steal.
I'm using the low-level datastore API. In my app, users will be
entering a SQL where clause. For instance:
category = "Java" and rating > 5
This translates to the com.google.a
wLevelQuery( "select from myKind where
> category = 'Java' and rating > 5" );
> List results = myQuery.asList();
>
> Let me know what you think.
>
> Vince
>
> On Wed, Jan 6, 2010 at 3:06 PM, keyurva wrote:
> > This is likely a common scen
This has to be the first query that works but somehow for me a simple
EQUAL operator on a string property does not yield results. I'm using
the low level datastore api. Now it could be that this is only a local
datastore issue and once deployed on app engine it does work. But I'd
like someone to co
This is where embarrassment becomes me. This issue was a false alarm.
A case of corrupt data.
Sorry for the trouble.
== Keyur
On Feb 23, 1:37 pm, keyurva wrote:
> This has to be the first query that works but somehow for me a simple
> EQUAL operator on a string property does not yield r
I understand that the official docs for the Java bulkloader are
currently being worked on.
In the interim is it possible to get any kind of sample code that we
can look at?
Thanks,
Keyur
--
You received this message because you are subscribed to the Google Groups
"Google App Engine for Java" g
I use the low-level datastore API. At runtime, I want to use the new
eventual consistency on occasions and strong consistency at others.
I was looking at the Query class to set the consistency option but
noticed that it is only available in DatastoreServiceConfig. Is it
expected that one needs to
Thanks.
On Apr 1, 4:29 pm, "Ikai L (Google)" wrote:
> That's correct. The cost of creating an instance is negligible, though. It's
> not dissimilar to creating different MemcacheService instances with
> different write policies.
>
>
>
> On Thu, Apr 1, 2
In my application, I create a DatastoreService instance, maintain a
reference to it and use it for the life of that instance of the
application.
In another discussion I learned that the cost of creating a new
DatastoreService instance is negligible.
Given that, is it still advisable for me to mai
e each service by config or create a new one each time.
> > If I were writing code by hand I would choose the simple option of creating
> > one as needed with the options you want at the time.
>
> > On 2 Apr 2010, at 08:09, keyurva wrote:
>
> >> In my application
writing code by hand I would choose the simple option of creating
> > one as needed with the options you want at the time.
>
> > On 2 Apr 2010, at 08:09, keyurva wrote:
>
> >> In my application, I create a DatastoreService instance, maintain a
> >> reference to
different write policies.
>
> > On Thu, Apr 1, 2010 at 4:09 PM, keyurva wrote:
> > > I use the low-level datastore API. At runtime, I want to use the new
> > > eventual consistency on occasions and strong consistency at others.
>
> > > I was looking at the Query clas
Currently to upload blobs, the blob store service creates a unique one-
time URL that a user can post blobs to. My requirement is that I only
want authenticated / authorized users to post blobs in my application.
I can achieve this currently if the page that includes the multipart
form to upload bl
I have an interesting problem with my blob store fetches - I need to
fetch 2 chunks of data 5 bytes each that are 1000 bytes apart.
>From the perspective of the BlobstoreService, is it more efficient for
me to make 2 fetchData calls of 5 bytes each or 1 fetchData call of
1010 bytes?
Thanks,
Keyur
Submitted a new feature request for this:
http://code.google.com/p/googleappengine/issues/detail?id=3160
== Keyur
On Apr 26, 1:57 pm, keyurva wrote:
> Currently to upload blobs, the blob store service creates a unique one-
> time URL that a user can post blobs to. My requirement is that
Can someone confirm or refute if the MemcacheService is LRU or not?
I'm looking to implement a sliding expiration within the memcache
service but if it is already an LRU then I don't need to bother.
Thanks,
Keyur
--
You received this message because you are subscribed to the Google Groups
"Goog
that are sometimes badly translated.
> > If were you i'elle explain what you are thinking of by LRU.
>
> > Le 30 avr. 2010 20:02, "keyurva" a écrit :
>
> > Can someone confirm or refute if the MemcacheService is LRU or not?
> > I'm looking to imple
I'm using the low-level datastore api and I want to query by the key
property and another property (let's call it category). So the query
filter would be: __key__ IN [k1, k2, ..., kn] and category=foo
I need to query based on a list of keys for which I'll use the IN
operator. I know that the max.
On the dev server I call setHeader() on the response but it doesn't
seem to set it - coz when I call containsHeader() immediately after
calling setHeader() it returns false.
response.setHeader("Content-Encoding", "gzip");
logger.info(response.containsHeader("Content-Encoding")); //prints
false
Is
I am querying the __Stat_Kind__ kind. It does not return me entities
about kinds that currently exist in the datastore but it includes
entities about kinds that I had deleted more than a week ago.
I am not so much concerned about it returning me the non-existent
kinds - the doc does mention this s
I have a Java app deployed on app engine and I use appcfg.py of the
Python SDK to vacuum and update my indexes.
Today I first ran vacuum_indexes and that completed successfully -
i.e. it en-queued tasks to delete my existing indexes.
The next step was probably a mistake on my part - I then ran
up
Can someone on the app engine team help me out?
Thanks,
Keyur
On Jun 10, 5:45 pm, keyurva wrote:
> I have a Java app deployed on app engine and I use appcfg.py of the
> Python SDK to vacuum and update my indexes.
>
> Today I first ran vacuum_indexes and that completed successfully
he indexes you want to be created in index.yaml
5. Run update_indexes
6. Look at your app's admin console and it should show that your
indexes are now building.
7. Enjoy the fruits of your labor :)
Cheers,
Keyur
On Jun 11, 9:45 am, keyurva wrote:
> Can someone on the app engin
The BlobstoreService recently added support for serving partial byte
ranges from a blob. When this method is invoked the response is
generated with a HTTP 206 (Partial Content) status code. So it looks
like app engine assumes that it is always serving a Range request in
this case.
However, in my c
23 matches
Mail list logo
