[google-appengine] Re: Problem in Full Text Search - com.google.appengine.api.search.SearchException: Transient error, please try again.

2014-01-10 Thread husayt
We had the same at the same time/

On Friday, 10 January 2014 17:15:07 UTC, Ananthakrishnan Venkatasubramanian 
wrote:
>
> Hi,
>
>
> We are a premium account user. We are in the process of implementing 
> full-text search in our application developed using Java. While searching 
> for documents in an index with pagination using cursor, at one point of 
> time we are getting the following exception as we paginate. Pagination does 
> work for most of the cases though and then fails at some point of time with 
> the exception.
>
>
> *com.google.appengine.api.search.SearchException: Transient error, please 
> try again.*
>
> at 
> com.google.appengine.api.search.IndexImpl$4.convertException(IndexImpl.java:345)
>
> at com.google.appengine.api.utils.FutureWrapper.get(FutureWrapper.java:94)
>
> at 
> com.google.appengine.api.search.FutureHelper.getInternal(FutureHelper.java:73)
>
> at 
> com.google.appengine.api.search.FutureHelper.quietGet(FutureHelper.java:32)
>
> at com.google.appengine.api.search.IndexImpl.search(IndexImpl.java:497)
>
>
> Please provide us a direction as to how to solve this problem.
>
>
> Thanks.
>
>
> Regards,
>
> Anantha Krishnan.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/groups/opt_out.


[google-appengine] 1.8.9 Pre-Release SDKs are now available.

2014-01-10 Thread Richmond Manzana
Happy New Year!

We wanted to inform you that the pre-release SDKs for Python, PHP and Java 
are now available and are found here:
http://code.google.com/p/googleappengine/downloads/list

Please see the pre-release notes below.

Cheers,

Richmond Manzana
Technical Program Manager
Google App Engine

App Engine SDK - Pre-Release Notes

Version 1.8.9

Python & PHP
==
- Renamed appcfg start to appcfg start_module_version and stop to
  stop_module_version.
- Fixed an issue with ID allocation collisions in the Datastore.
  https://code.google.com/p/googleappengine/issues/detail?id=10134
- Fixed an issue with Cloud Storage calls failing in the dev_appserver.
https://code.google.com/p/googleappengine/issues/detail?id=10181
https://code.google.com/p/googleappengine/issues/detail?id=10185
- Fixed an issue with the dev_appserver not starting on Windows when using
  versions of Python earlier than 2.7.2.
https://code.google.com/p/googleappengine/issues/detail?id=10363


Python
==
- Deprecated start_module, start_module_async, stop_module, 
stop_module_async
  get_modules_async, get_versions_async, get_default_version_async,
  get_num_instances_async, get_hostname_async and added start_version,
  start_version_async, stop_version, stop_version_async as replacements in 
the
  Modules API.
- Added verbose_name support for ComputedProperty in NDB.
https://code.google.com/p/appengine-ndb-experiment/issues/detail?id=239
- Fixed an issue with deffered.defer not waiting for async operations.
https://code.google.com/p/appengine-ndb-experiment/issues/detail?id=238
- Fixed an issue with LocalStructureProperty not handling None value in NDB.
https://code.google.com/p/appengine-ndb-experiment/issues/detail?id=233
- Fixed an issue NDB not working with sqlite.
https://code.google.com/p/googleappengine/issues/detail?id=8381
- Fixed an issue with debug not working with PyDev in 1.8.8.
https://code.google.com/p/googleappengine/issues/detail?id=10390
- Fixed an issue with object properties not being retrieved in NDB.
https://code.google.com/p/googleappengine/issues/detail?id=10467


PHP
=
- Renamed startModule, stopModule to startVersion, stopVersion in the 
Modules
  API.
- Added support for the ftp extension.
- Added support for the zip extension.
- Added support for the gethostname() function.
- A proper "billing required" message is now given when users attempt to use
  Sockets API on free apps.
- Fixed an issue with header keys and values having whitespaces preventing
  responses from being compressed.
- Fixed an issue with content-type and metadata not being updated when 
renaming
  Google Cloud Storage objects.
- Fixed an issue with Cloud Storage rename requests failing when an object 
has
  a space in its name.


Java
==
- Renamed appcfg start to appcfg start_module_version and stop to
  stop_module_version.
- The following methods are deprecated in the Modules API and will be 
removed
  in an upcoming release:
getModulesAsync
getVersionsAsync
getDefaultVersionAsync
getNumInstancesAsync
getVersionHostnameAsync
getInstanceHostnameAsync
startModule (replaced by startVersion)
startModuleAsync (replaced by startVersionAsync)
stopModule (replaced by stopVersion)
stopModuleAsync (replaced by stopVersionAsync)
getModuleHostname (replaced by getVersionHostname and 
getInstanceHostname)
getModuleHostnameAsync
- The following exceptions have been deprecated in the Modules API and will 
be
  removed in a following release:
InvalidInstanceException
InvalidModuloeException
InvalidVersionException
- The following exceptions have been removed in the Modules API:
ModuleAlreadyStartedException
ModuleAlreadyStoppedException
- Modules are now supported in the dev_appserver Development Console.
- Fixed an issue with ID allocation collisions in the Datastore.
  https://code.google.com/p/googleappengine/issues/detail?id=10134

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/groups/opt_out.


[google-appengine] Re: BlobInfo entities in datastore for files in Google Cloud Storage?

2014-01-10 Thread Vinny P
On Friday, January 10, 2014 11:59:04 AM UTC-6, AndyD wrote:

> Is there a way to store files in GCS using the BlobstoreService's upload 
> URL without having these BlobInfo entities getting created in the 
> datastore?  If not, do I actually need them (can I delete them)?
>
>

Even though the files are stored in GCS, the Blobstore service generates 
the BlobInfo entities so it can keep track of all the uploaded files. If 
you delete anything, it may cause unstable behavior. If I recall correctly, 
these blobinfo entities are considered protected (either you can't delete 
them, or they'll be regenerated).

If you want to avoid creating BlobInfo entities, you'll have to find some 
other way of processing uploaded files. If the incoming files are less than 
32MB, you can simply handle them in the POST handler. If the incoming files 
are larger, you may want to look into Signed URLs: 
https://developers.google.com/storage/docs/accesscontrol#Signed-URLs (be 
sure to read the note in the gray box). 


-
-Vinny P
Technology & Media Advisor
Chicago, IL

App Engine Code Samples: http://www.learntogoogleit.com  

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/groups/opt_out.


[google-appengine] RPC (urlfetch) errors again

2014-01-10 Thread GAEfan
We are still having a large number of urlfetches timeout.  It appears to be 
a DNS issue, as they run perfectly from development server every time, and 
I get hit them manually perfectly every time.

Last time, we were told. "The problem appears to be limited to hosts behind 
one network provider. We're in contact with the network provider and 
working on getting the problem resolved."

But, the problem seems to come and go intermittently.  Can this please be 
fixed?

We get messages in the logs like, "2014-01-10 09:50:45.856 Found 2 RPC 
request(s) without matching response (presumably due to timeouts or other 
errors)"

These RPC requests seem to go nowhere, and just timeout.  The destination 
URLs never get hit.
Can someone at Google please look into this?
Thank you.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/groups/opt_out.


[google-appengine] BlobInfo entities in datastore for files in Google Cloud Storage?

2014-01-10 Thread AndyD
My GAE application allows clients to upload files.  The app implements the 
upload functionality using upload URLs generated by the BlobstoreService, 
configured to store the files in GCS (not the Blobstore).  When my app 
receives the post-upload callback request from the BlobstoreService, I 
extract the filename of the uploaded file, and save it in an entity in the 
datastore, which allows later access to the file in GCS.  

Since I'm not storing the files in the Blobstore, I'm surprised to find 
that each file stored in GCS has a corresponding BlobInfo entity in the 
datastore.  Since these seem to be averaging about 2KB in size, it's 
turning out to be quite a bit of storage for something I'm not using.

Is there a way to store files in GCS using the BlobstoreService's upload 
URL without having these BlobInfo entities getting created in the 
datastore?  If not, do I actually need them (can I delete them)?

-Andy

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/groups/opt_out.


[google-appengine] Re: Problem in Full Text Search - com.google.appengine.api.search.PutException: Failed to complete request in 5622ms

2014-01-10 Thread Vinny P
On Friday, January 10, 2014 11:06:33 AM UTC-6, Ananthakrishnan 
Venkatasubramanian wrote:

> We are in the process of implementing full-text search in our application 
> developed using Java. While writing a document to an index, we are facing 
> the failure sometimes sporadically and not always. Here's the following 
> exception stacktrace for the same.
>
> *com.google.appengine.api.search.PutException: Failed to complete request 
> in 5622ms*
>
> Please provide us a direction as to how to solve this problem. 
>



Transient errors happen sometimes, it's just a fact of life with the Search 
API. How many put operations are failing with this exception?

What I would recommend is catching the exception and checking whether it is 
a transient issue. You can do this by comparing *StatusCode.TRANSIENT_ERROR*
 and *[the caught exception].getOperationResult().getCode()* and checking 
if they are equal. If so, just retry the put operation. 


-
-Vinny P
Technology & Media Advisor
Chicago, IL

App Engine Code Samples: http://www.learntogoogleit.com  

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/groups/opt_out.


[google-appengine] Re: User facing requests going into the warm up instances and getting served

2014-01-10 Thread Vinny P
On Friday, January 10, 2014 7:58:54 AM UTC-6, Ian Marshall wrote:

> You could increase your pending latency settings to the maximum allowed, 
> in order to try to have your app wait as long as possible for an existing 
> app instance to serve a web request. I use:
>
>   
> 1
> automatic
> 15.0s
> automatic
> [...]
>   
>
> to implement this, but I still get web requests being directed to a new 
> app instance which has just been launched and therefore is not ready to 
> serve immediately.
>
>>
>>

+1.

The suggestions above are all good ideas, but regardless of the settings 
you choose there are always going to be some requests that initiate 
instance startup. How many requests (as a percentage of all requests) are 
causing instance startup in your application?

In my experience, whenever App Engine gets more aggressive in starting up 
instances means that there's a new version of App Engine coming out. That 
or someone at Google is tinkering with the scheduler :-). 

-
-Vinny P
Technology & Media Advisor
Chicago, IL

App Engine Code Samples: http://www.learntogoogleit.com 

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/groups/opt_out.


[google-appengine] Problem in Full Text Search - com.google.appengine.api.search.SearchException: Transient error, please try again.

2014-01-10 Thread Ananthakrishnan Venkatasubramanian
 

Hi,


We are a premium account user. We are in the process of implementing 
full-text search in our application developed using Java. While searching 
for documents in an index with pagination using cursor, at one point of 
time we are getting the following exception as we paginate. Pagination does 
work for most of the cases though and then fails at some point of time with 
the exception.


*com.google.appengine.api.search.SearchException: Transient error, please 
try again.*

at 
com.google.appengine.api.search.IndexImpl$4.convertException(IndexImpl.java:345)

at com.google.appengine.api.utils.FutureWrapper.get(FutureWrapper.java:94)

at 
com.google.appengine.api.search.FutureHelper.getInternal(FutureHelper.java:73)

at 
com.google.appengine.api.search.FutureHelper.quietGet(FutureHelper.java:32)

at com.google.appengine.api.search.IndexImpl.search(IndexImpl.java:497)


Please provide us a direction as to how to solve this problem.


Thanks.


Regards,

Anantha Krishnan.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/groups/opt_out.


[google-appengine] Problem in Full Text Search - com.google.appengine.api.search.PutException: Failed to complete request in 5622ms

2014-01-10 Thread Ananthakrishnan Venkatasubramanian
 

Hi,

We are a premium account user. We are in the process of implementing 
full-text search in our application developed using Java. While writing a 
document to an index, we are facing the failure sometimes sporadically and 
not always. Here's the following exception stacktrace for the same.

*com.google.appengine.api.search.PutException: Failed to complete request 
in 5622ms*

at com.google.appengine.api.search.IndexImpl$3.wrap(IndexImpl.java:306)

at com.google.appengine.api.search.IndexImpl$3.wrap(IndexImpl.java:285)

at 
com.google.appengine.api.utils.FutureWrapper.wrapAndCache(FutureWrapper.java:53)

at com.google.appengine.api.utils.FutureWrapper.get(FutureWrapper.java:90)

at 
com.google.appengine.api.search.FutureHelper.getInternal(FutureHelper.java:73)

at 
com.google.appengine.api.search.FutureHelper.quietGet(FutureHelper.java:32)

at com.google.appengine.api.search.IndexImpl.put(IndexImpl.java:478)


Please provide us a direction as to how to solve this problem. 

Thanks in advance for the solution.


Regards,

Anantha Krishnan

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/groups/opt_out.


[google-appengine] Re: Unable to insert a file in a particular folder

2014-01-10 Thread Vinny P
On Friday, January 10, 2014 9:19:19 AM UTC-6, Pravanjan Niranjan wrote:

> We have rest full integration with drive . 
>
> Every time i try to create  a file inside a particular folder this just 
> create in my default drive space.
>
>
> JsonObject jsonObject = new JsonObject();
>
> jsonObject.addProperty("title", "newfile.doc");
>
> jsonObject.addProperty("mimeType", 
> "application/vnd.google-apps.document");
>
> jsonObject.addProperty("parents", "["+parents+"]");
>
> String responseString = 
> UrlFetchServiceUtil.GoogleDriveinFetch(driveURl, jsonObject.toString(), 
> "POST", "application/json",access_Token);
>
>
> This create file with default space . please help.
>
>
>
What type of object is paramMap? If it's the standard Java map 
implementation in java.util.*, it may not be serializing into valid 
JSON. Can you print out the contents of the jsonObject and post it here?


-
-Vinny P
Technology & Media Advisor
Chicago, IL

App Engine Code Samples: http://www.learntogoogleit.com

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/groups/opt_out.


[google-appengine] GAE cost projection calculator - anybody got a good spreadsheet template they could share?

2014-01-10 Thread AndyD
I'm working up a spreadsheet to help project GAE costs for an application. 
 Basically I want to do stuff like:

   - enumerate all the kinds of requests the service will be receiving, and 
   for each one identify the number of datastore small/read/write operations 
   per request, the number of requests/day, then factor in the daily free 
   quota and the cost per small/read/write op over the quota.  
   - For each request type, estimate the frontend/backend CPU time per 
   request, add it all up per day, apply the quotas, cost per unit time over 
   quota, etc.
   - enumerate all the datastore entity kinds I'll be storing, how big each 
   is on average, how many of them there will be, then factor in the free 
   quota and the monthly charge per GB over that quota
   - and so on for things like network trafffic, all the other APIs that 
   have free quotas and over-quota costs, you get the idea...


So... obviously I'm not the first person to ever do this.  If you've put 
together a useful spreadsheet template, how about sharing?

-Andy Dennie


-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/groups/opt_out.


[google-appengine] Problem in Full Text Search - com.google.appengine.api.search.SearchException: Transient error, please try again.

2014-01-10 Thread Ananthakrishnan Venkatasubramanian
Hi,

We are a premium account user. We are in the process of implementing 
full-text search in our application developed using Java. While searching 
for documents in an index with pagination using cursor, at one point of 
time we are getting the following exception as we paginate. Pagination does 
work for most of the cases though and then fails at some point of time with 
the exception.

*com.google.appengine.api.search.SearchException: Transient error, please try 
again.*
at 
com.google.appengine.api.search.IndexImpl$4.convertException(IndexImpl.java:345)
at 
com.google.appengine.api.utils.FutureWrapper.get(FutureWrapper.java:94)
at 
com.google.appengine.api.search.FutureHelper.getInternal(FutureHelper.java:73)
at 
com.google.appengine.api.search.FutureHelper.quietGet(FutureHelper.java:32)
at com.google.appengine.api.search.IndexImpl.search(IndexImpl.java:497)
at 
com.adaptavant.distributedsource.dao.SearchDAO.readIndex(SearchDAO.java:683)
at 
com.adaptavant.distributedsource.service.SearchService.searchSimilarContacts(SearchService.java:3336)
at 
com.adaptavant.distributedsource.controller.SearchController.searchSimilarContacts(SearchController.java:253)
at sun.reflect.GeneratedMethodAccessor231.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
com.google.apphosting.runtime.security.shared.intercept.java.lang.reflect.Method_$1.run(Method_.java:179)
at java.security.AccessController.doPrivileged(Native Method)
at 
com.google.apphosting.runtime.security.shared.intercept.java.lang.reflect.Method_.privilegedInvoke(Method_.java:176)
at 
com.google.apphosting.runtime.security.shared.intercept.java.lang.reflect.Method_.invoke_(Method_.java:137)
at 
com.google.apphosting.runtime.security.shared.intercept.java.lang.reflect.Method_.invoke(Method_.java:45)
at 
org.springframework.web.method.support.InvocableHandlerMethod.invoke(InvocableHandlerMethod.java:219)
at 
org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:132)
at 
org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:104)
at 
org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandleMethod(RequestMappingHandlerAdapter.java:745)
at 
org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:686)
at 
org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:80)
at 
org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:925)
at 
org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:856)
at 
org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:936)
at 
org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:838)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
at 
org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:812)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at 
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
at 
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1166)
at 
com.adaptavant.distributedsource.filter.JsonpCallbackFilter.doFilter(JsonpCallbackFilter.java:62)
at 
org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:346)
at 
org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:259)
at 
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at 
com.google.apphosting.utils.servlet.ParseBlobUploadFilter.doFilter(ParseBlobUploadFilter.java:125)
at 
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at 
com.google.apphosting.runtime.jetty.SaveSessionFilter.doFilter(SaveSessionFilter.java:35)
at 
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at 
com.google.apphosting.utils.servlet.JdbcMySqlConnectionCleanupFilter.doFilter(JdbcMySqlConnectionCleanupFilter.java:60)
at 
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at 
com.google.apphosting.utils.servlet.TransactionCleanupFilter.doFilter(TransactionCleanupFilter.java:43)
at 
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at 
org.mortbay.jetty.servlet.Se

[google-appengine] Premier Billing - Stuck in Limbo

2014-01-10 Thread OC2PS
Since my readers (and I) are based in Europe, I wanted to have my app (and 
db) to be located in Europe. As it turns out, you can only do that if you 
have a Premier Account. Fine, I ground my teeth and clicked the button to 
apply for a Premier Account.

That was 40 days ago! Till date, I haven't heard back, and my billing 
status still says

> Billing Status: Premier Billing Requested
>
> An admin of your application has requested premier billing from 
> mydomain.tld. You will not be able to make other billing changes while the 
> premier request is outstanding.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/groups/opt_out.


[google-appengine] Unable to insert a file in a particular folder

2014-01-10 Thread Pravanjan Niranjan
We have rest full integration with drive . 

Every time i try to create  a file inside a particular folder this just 
create in my default drive space.


  paramMap.put("kind","drive#parentReference");

 paramMap.put("id","0B0Rxcic23Cs6RlhJc3dCbG1jY1k")

  Writer strWriter = new StringWriter();

try{

   mapper.writeValue(strWriter, paramMap);

String parents = strWriter.toString();

 

JsonObject jsonObject = new JsonObject();

jsonObject.addProperty("title", "newfile.doc");

jsonObject.addProperty("mimeType", 
"application/vnd.google-apps.document");

jsonObject.addProperty("parents", "["+parents+"]");

 

String access_Token =  
updateAccessTokenWithResfreshToken(refreshToken);



String responseString = 
UrlFetchServiceUtil.GoogleDriveinFetch(driveURl, jsonObject.toString(), 
"POST", "application/json",access_Token);


This create file with default space . please help.


-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/groups/opt_out.


[google-appengine] Incomplete docs for dispatch.xml

2014-01-10 Thread Tapir
This docs "Routing Requests to Modules" for java
https://developers.google.com/appengine/docs/java/modules/routing
doesn't mention to make a dispatch file applied,

   appcfg update_dispatch default/war

muse be called. 

Wasted me another day.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/groups/opt_out.


[google-appengine] Incomplete docs for dispatch.xml

2014-01-10 Thread Tapir
This docs "Routing Requests to Modules" for java
https://developers.google.com/appengine/docs/java/modules/routing
doesn't mention to make a dispatch file applied,

   appcfg update_dispatch default/war

muse be called. 

Wasted me another day.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/groups/opt_out.


[google-appengine] Re: User facing requests going into the warm up instances and getting served

2014-01-10 Thread Ian Marshall
You could increase your pending latency settings to the maximum allowed, in 
order to try to have your app wait as long as possible for an existing app 
instance to serve a web request. I use:

  
1
automatic
15.0s
automatic
[...]
  

to implement this, but I still get web requests being directed to a new app 
instance which has just been launched and therefore is not ready to serve 
immediately.


On Friday, 10 January 2014 06:23:09 UTC, aswath wrote:
>
> Hello,
>
> The user facing requests are going into the instance startup and getting 
> served.   Any settings recommended recently for avoiding this.
>
> My settings are 
>
> instance_class: F2
>
> automatic_scaling:
>   min_idle_instances: 1
>
>   max_idle_instances: 1
>   min_pending_latency: 5.8s
>
>   max_pending_latency: 5.8s
>
>
> -Aswath
> www.accountingguru.net.
>  

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/groups/opt_out.


[google-appengine] minimum cost when creating new entity is two writes, can it ever be just one ?

2014-01-10 Thread James Gilliam
It appears the minimum cost when creating a new entity is one put and one 
index write; this occurs when nothing is explicitly indexed in the entity.  

Even with nothing explicitly indexed in the entity, the entity name is 
always indexed.

The single index write is presumably for the negative index on the name, 
but many times you don't need the negative index.

Is there any way to avoid the index write when creating a new entity?

Or equivalently, could GAE not charge for the index write on the name of 
the entity?

Thanks

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/groups/opt_out.


[google-appengine] Re: User facing requests going into the warm up instances and getting served

2014-01-10 Thread Aswath Satrasala
Yes, it is enabled.


On Fri, Jan 10, 2014 at 3:54 PM, timh  wrote:

> You do have warmup requests enabled ?
>
>
> On Friday, January 10, 2014 2:23:09 PM UTC+8, aswath wrote:
>>
>> Hello,
>>
>> The user facing requests are going into the instance startup and getting
>> served.   Any settings recommended recently for avoiding this.
>>
>> My settings are
>>
>> instance_class: F2
>>
>> automatic_scaling:
>>   min_idle_instances: 1
>>
>>   max_idle_instances: 1
>>   min_pending_latency: 5.8s
>>
>>   max_pending_latency: 5.8s
>>
>>
>> -Aswath
>> www.accountingguru.net.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/groups/opt_out.


[google-appengine] How can I be a google OAuth2.0 service provider for non gae applications?

2014-01-10 Thread sarath upadrista
Hi,
 I would like my appengine application to be a OAuth2.0 Service
provider for the non gae applications. I use Google appengine java in my
application. I have been searching for long time but I am not getting
enough documentation. Can anybody provide sample gaej project which will be
a OAuth2.0 Service provider and supports non gae applications.

-- 
Thanks & Regards
Sarath U

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/groups/opt_out.


[google-appengine] Re: User facing requests going into the warm up instances and getting served

2014-01-10 Thread timh
You do have warmup requests enabled ?

On Friday, January 10, 2014 2:23:09 PM UTC+8, aswath wrote:
>
> Hello,
>
> The user facing requests are going into the instance startup and getting 
> served.   Any settings recommended recently for avoiding this.
>
> My settings are 
>
> instance_class: F2
>
> automatic_scaling:
>   min_idle_instances: 1
>
>   max_idle_instances: 1
>   min_pending_latency: 5.8s
>
>   max_pending_latency: 5.8s
>
>
> -Aswath
> www.accountingguru.net.
>  

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/groups/opt_out.


[google-appengine] Re: User facing requests going into the warm up instances and getting served

2014-01-10 Thread Ian Marshall
All I can suggest is starring Issue 7865 (User-facing requests should never 
be locked to cold instance starts) at 
http://code.google.com/p/googleappengine/issues/detail?id=7865.


On Friday, 10 January 2014 06:23:09 UTC, aswath wrote:
>
> Hello,
>
> The user facing requests are going into the instance startup and getting 
> served.   Any settings recommended recently for avoiding this.
>
> My settings are 
>
> instance_class: F2
>
> automatic_scaling:
>   min_idle_instances: 1
>
>   max_idle_instances: 1
>   min_pending_latency: 5.8s
>
>   max_pending_latency: 5.8s
>
>
> -Aswath
> www.accountingguru.net.
>  

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/groups/opt_out.