Hi!
I'm experiencing a strange problem with file uploads to Blobstore (runtime:
Java). POSTing a request with file data from client's browser to Blobstore
service URL (retrieved by a call to createUploadUrl()) causes a status 500
response with no explanation. Request is never redirected to my se
Hi!
I'm using CloudSQL with Hibernate (v 4.1.7), and sometimes opening new
connection to CloudSQL takes too much time. More specific, the problem is
in initialization of Bytecode provider. Usually it takes about 5 seconds,
but sometimes up to 40-50 seconds! This problem causes
DeadlineExceededE
t;
> The simplest workaround is to replace -dot-latest-dot- with just -dot-.
>
>
> On Monday, December 31, 2012 3:36:49 AM UTC-8, Oleg Bashtenko wrote:
>>
>> Hi guys!
>>
>> I've got a big problem with Datastore Admin. I have two Java applications
>&
Hi guys!
I've got a big problem with Datastore Admin. I have two Java applications
with IDs '*dev-tcs*' and '*teamwork-client-services*'. Both of them have a
non-default Python version for Datastore Admin purposes. In the first one,
Datastore Admin works perfectly. But in the second one, I can'
Bingo! That works now.
Thanks guys for your help and useful information. My app is working
perfectly now, and I can run advanced search queries on any combination of
fields with only 66 indexes on that entity kind (this is acceptable for my
purposes).
Good luck to all your team!
Best regards,
O
Oops. Thank you. Looks like that I forgot to remove one more inequality
constraint. This query:
com.googlecode.objectify.impl.QueryImpl{kind=Ticket,ancestor=,filter=
activeEQUALtrue,filter=technicianKeyEQUALUser("tech"),filter=vipEQUALtrue,
sort=techPriorityLevelASCENDING,limit=10}
works OK, but
No, I'm working with objectify-appengine. May it cause such problem? There
are only equality filters in my query, and one ordering field. Everything
works OK if I define such composite index on all fields used in the query,
but the point is to avoid that since there are too many possible
combin
Got another problem.
There is a "Ticket" kind in my datastore. I want to run a search query on a
several fields, e.g.: { active, technicianKey, vip, dueDate } and order
results by {techPriorityLevel} field (ascending).
According to article you recommended, it's not necessary for me to define a
c
Thank you very much for that information!
It seems that your improved Query Planner will GREATLY help me with my
indexing problem. I have a situation very similar to the one described in
that doc (custom search on any combination of properties), and now it looks
like that I'll not have to rejec
I have the same problem. I've got 224 (!) indices stuck in "Building..."
state and unable to do anything to them (vacuum_indexes doesn't help). My
app ID is "dev-tcs" (HRD).
Actually, most of those indices were created by mistake, and now I can't do
anything (including creation of correct indice
10 matches
Mail list logo
