Paul, yes.
Whenever you update an entity, any property that is not explicitly marked
as unindexed will generate 2 index writes. Any update to that property will
cause 2 writes to delete the old indexes and 2 writes to write the new
ones. The indexes are used in queries, e.g.:
select from user whe
Also, another question:
I don't even have datastore-indexes.xml generated, should I even have
any index write ops possible without it?
--
You received this message because you are subscribed to the Google Groups
"Google App Engine for Java" group.
To post to this group, send email to google-app
@Extension(vendorName "datanucleus", key "gae.
unindexed", value"true")
I don't know if it works though. I am still getting mysterious
"Datastore Index Write Ops". About 4.5k a day, from only pinging my
main page, which does not save anything to DB. Anyone has any idea
what it may be? Or how to ch
Suresh,
You can use JDO or JPA APIs instead of using the datastore API directly if
you are familiar with those and if you need to someday migrate to some
RDBMS or even Google Cloud SQL which is in the works.
If you have not already, I would strongly suggest you start with
http://code.google.c
Hi Mukesh,
I am new to GAE. Can u guide me in using GAE DataStore in java and to
store and retrieve data's using DataStore. Any hands on Samples are
welcomed.
Regards,
Suresh
On Dec 22, 5:58 am, Mukesh Joshi wrote:
> I have the same question regarding unnecessary indexes and I am using JDO.
>
I have the same question regarding unnecessary indexes and I am using JDO.
I tried using setUnindexed but that did not seem to help.
What annotation are you using for individual fields ?
--
You received this message because you are subscribed to the Google Groups
"Google App Engine for Java" g
Ah it would have helped if I'd read your original post - I believe (and I
haven't bothered with DataNucleus for a long time) that you need to add
that annotation for every property you wish to be unindexed.
Cheers,
Simon
--
You received this message because you are subscribed to the Google Gro
Yes, that's completely possible.
What persistence framework are you using, or are you using the low level
API? They all have different ways of turning off individual property
indexes. It should also be noted that once you change configuration, you
actually have to load and re-persist all of y
1 hour video? Nice :)
I have rather big entity, with over 100 properties, I will query maybe
on 5 of them, so I was wondering if I can turn off indexing for all of
them and just on for those 5.
On Dec 14, 10:39 pm, "Ikai Lan (Google)" wrote:
> Every property creates 2 indexes, so if you don't
