Re: [google-appengine] Re: AppEngine and Adwords Api
On Tue, Apr 16, 2013 at 11:15 PM, Vinny P vinny...@gmail.com wrote: From your StackOverflow post: It breaks in production - for instance: java.lang.SecurityException: java.lang.IllegalAccessException: Reflection is not allowed on private javax.xml.ws.wsaddressing.W3CEndpointReference$Address javax.xml.ws.wsaddressing.W3CEndpointReference.address You're attempting to package your own JAX-WS library, which is why AppEngine Production is complaining. AppEngine-Prod uses its own custom JAX-WS implementation, you cannot override that with your own bundled libraries (see here for some people with the same issue, search the page for the word jaxws http://code.google.com/p/googleappengine/issues/detail?id=4910 ). Try repackaging the libraries and skipping the XML parsing services. Some brief searching turns up this blog post, it looks like this guy solved the problem, but I haven't used the code myself so take it with a pinch of salt: http://penumbro.us/post/1135755221/adwords-api-on-app-engine-java-part-3 . Hi Vinny, thanks for your reply. I examined a bit (a lot - in fact) further and found more pointers. The result: Using adwords-appengine works in production after some tweaking (I'll write a blog post about that). But. I am getting security exceptions on the Java devserver. For instance: access denied (java.lang.RuntimePermission accessClassInPackage.com.sun.xml.internal.ws) So - to me - it seems my classpath is fine. But the devserver is enforcing something that is no problem in reality. Sounds strange to me - and is of course misleading... Does anyone have any ideas about that? Thanks! Raphael -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[google-appengine] Measuring code coverage of Google App Engine Apps (Java) using EclEmma
In case anyone is interested, this is how you can use EclEmma code coverage tool with GAE/J apps. The same content also available in this GoogleDochttps://docs.google.com/document/d/1qqwV_cwXaLA-1ldDN8m88BmwqsX_VziDuAqy6jWSAbU/pub?embedded=true . -- Measuring Code Coverage of Google App Engine Apps (Java) using EclEmma EclEmma http://www.eclemma.org/ is a free Code Coverage tool for Java. It comes as an Eclipse plugin. [image credit: eclemma.org] Out of the box, it cannot show code coverage of the server-side code (e.g., Servlets) of an GAE/J application. Here’s an easy workaround you can use to measure code coverage of an GAE/J app running on the dev server. The essence of this workaround is to collect coverage data from the dev server as as separate session and merge it with coverage data collected from JUnit tests. Here are the steps. Step 1. Create a ‘Coverage configuration’ for starting the Dev server. Use ‘Java Application’ as the type. Configure tabs such as ‘Man’ and ‘Arguments’ with the same parameter values you used when creating your normal ‘Run as web application’ configuration used to start the dev server normally. Step 2: Start the dev server in the coverage mode. That is, run the configuration you created above. Step 3: Run your unit tests in coverage mode. This can be done by right-clicking your JUnit class and choosing ‘Coverage as’ → ‘Junit test’ After this step, your ‘Coverage’ tab will show coverage results for tests that doesn’t involve the server. Step 4: Retrieve coverage data for server-side. For this, you can use the ‘dump execution data’ menu item. Step 5: Merge coverage data. Use the ‘merge sessions’ menu item to merge coverage data from the server-side and JUnit tests. Note: I found this workaround in this in a post by Richard Bergerhttp://sourceforge.net/projects/eclemma/forums/forum/614870/topic/5138797. The above is simply a detailed explanation of the same solution. -- [Author: Damith, from the TEAMMATES teamhttps://teammatesv4.appspot.com/about.html ] [Last edited: 17 Apr 2013] -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[google-appengine] Should I Implement the Search API?
I haven't even considered reading the Search API documents up until yesterday, the production limitations of the Search API made me consider it as a non-existent feature. However it seems a lot of time has passed since it was first introduced and after reading the documents, I really really want to use it. Is there any ETA for scalable production usage? Will it ever reach a point that Total Index Size/API Calls will be able to reach TB's/Millions? Looking forward to hearing experiences/knowledge around Search Feature. -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[google-appengine] Re: Sockets or Apple Push Notification support in Google App Engine
Here's a sample project that can use sockets on App Engine to send out push notifications on ios: https://github.com/GarettRogers/appengine-apns-gcm On Monday, February 13, 2012 11:42:43 AM UTC-8, Giant Fighting Robot wrote: I have outgrown the 3rd party options for push notifications to Apple devices. I heard rumors that Google was planning to add socket support to the app engine which would enable me to roll my own push notifications. I'm starting to think that was Channels, which doesn't appear to do what I need. My questions are: 1) To double check, does the App Engine allow for apple push notifications without going through a 3rd party service? (maybe it was added in and I missed it?) 2) Assuming no, are there any plans to support it in the near future? I don't need a date, but if it's expected in the coming months I might grin and bear it until support comes, or if it's completely orthogonal to GAE's plans, I'd love to hear that so I can plan accordingly. -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[google-appengine] Djangoform not supported anymore for python2.7, Any recommendation for replacement
Hi, I have a very large application hosted on google appengine which uses many djangoforms. Since now djangoform is not supported by google appengine anymore, I need to replace all of them, but I really don't want to, because there are so many of them. Is there any way I can put the djangoform back into my application? Peter -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[google-appengine] Re: Having a problem accessing Remote API for Java via proxy
Hi Moga, Even i am facing the issue now. Did you get any solution for this issue? On Wednesday, 21 November 2012 10:10:18 UTC+5:30, moga wrote: I am writing a program to access from a client environment to Remote API. However, the remote access via proxy server is not working properly. Would you please see where the problem is? (reference) https://developers.google.com/appengine/docs/java/tools/remoteapi#Configuring_Remote_API_on_the_Client Below is the program. System.setProperty(http.proxyHost, proxy.com); System.setProperty(http.proxyPort, 8080); System.setProperty(https.proxyHost, proxy.com); System.setProperty(https.proxyPort, 8443); RemoteApiOptions options = new RemoteApiOptions() .server(your_app_id.appspot.com, 443) .credentials(username, password); RemoteApiInstaller installer = new RemoteApiInstaller(); installer.install(options); installer.uninstall(); It works fine when (1)accessing by Remote API(not via proxy server), (2)accessing via proxy server by URL Connection. Thus, my guess is the problem is the proxy server setting to Remote API. -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [google-appengine] Re: Google App Engine SDK 1.7.7 is now available!
Hi, is there any progress on releasing an update for 1.7.7? This issue with jar splitting is stopping us from switching to 1.7.7. Thanks. On Thursday, 11 April 2013 19:45:42 UTC+1, Takashi Matsuo (Google) wrote: On Thu, Apr 11, 2013 at 10:49 AM, Ludovic Champenois lu...@google.comjavascript: wrote: Hi, We are tracking this issue internally...Only on windows, and if your app is using some JSP right? It's a combination of 2 things: the api jar becoming too big (we will compress it soon), and the jspc compiler keeping a lock on the files in the jspc classpath, making the api jar not deletable (we do not need to upload it to the runtime server)... Windows file locking system makes the locked file non deletable... Until we push a new SDK, the only workaround would be for you to modify your local SDK this way: 1/ unjar the impacted jar. 2/ rejar it with the jar command default (i.e compression) and making sure you keep all the META-INF manifest (using the m flag) content in the new jar. It contains critical info for the processing. This will workaround the issue, while waiting for a new push. To clarify, we're going to release a minor update for 1.7.7. For the meantime, you can re-jar the file as follows: cd to the working directory $ jar xf somewhere\appengine-java-sdk-1.7.7\lib\user\ appengine-api-1.0-sdk-1.7.7.**jar $ jar cfm somewhere\appengine-api-1.0-sdk-1.7.7.**jar META-INF/MANIFEST.MF * and replace the old jar with the newly created one. Sorry for the inconvenience. On Wednesday, April 10, 2013 2:35:01 PM UTC-7, Francois MASUREL wrote: Yes, without success. François Masurel On Wed, Apr 10, 2013 at 11:28 PM, Takashi Matsuo tma...@google.comwrote: Hi Francois, Thanks for the report. Have you tried it with --enable_jar_splitting? On Wed, Apr 10, 2013 at 1:59 PM, Francois Masurel f.ma...@gmail.comwrote: Getting also the same appengine-api-1.0-sdk-1.**7.7.**jar is too large error. I'm on Windows 7 x64 with latest GAE and Java 7 SDK and the appengine-api-1.0-sdk-1.7.**7.**jar is 30.6MB big. Thanx for your help. François On Wednesday, April 10, 2013 9:15:04 PM UTC+2, Sekhar wrote: I'm getting a appengine-api-1.0-sdk-1.7.7.**j**ar is too large error when deploying. Are we expected to split this manually or is there a workaround? On Tuesday, April 9, 2013 3:44:38 PM UTC-7, Richmond Manzana wrote: Hi everyone, We're happy to announce that we have released the 1.7.7 SDK. This release includes new features such as updates to the Maven Plugin, and Outbound Sockets. We're also happy to announce that we have removed the weekly $2.10 minimum spend for billing enabled apps :) For more details, please read our blog post and release notes. Announcement: http://googleappengine.**blogspo**t.com/2013/04/app-**engine-177-** released.htmlhttp://googleappengine.blogspot.com/2013/04/app-engine-177-released.html Releae notes for Python: http://code.google.com/p/**googl**eappengine/wiki/**SdkReleaseNote** s http://code.google.com/p/googleappengine/wiki/SdkReleaseNotes Release notes for Java: http://code.google.com/p/**googl**eappengine/wiki/**SdkForJavaRele** aseNoteshttp://code.google.com/p/googleappengine/wiki/SdkForJavaReleaseNotes Release notes for Go: https://code.google.com/p/**goog**leappengine/wiki/**SdkForGoRelea** seNoteshttps://code.google.com/p/googleappengine/wiki/SdkForGoReleaseNotes Cheers! Richmond Manzana Technical Program Manager Google App Engine -- 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-appengi...@**googlegroups.com. To post to this group, send email to google-a...@googlegroups.**com. Visit this group at http://groups.google.com/** group/google-appengine?hl=enhttp://groups.google.com/group/google-appengine?hl=en . For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out . -- Takashi Matsuo | Developers Programs Engineer | tma...@google.com -- You received this message because you are subscribed to a topic in the Google Groups Google App Engine group. To unsubscribe from this topic, visit https://groups.google.com/d/** topic/google-appengine/**r5JNlfkqq94/unsubscribe?hl=enhttps://groups.google.com/d/topic/google-appengine/r5JNlfkqq94/unsubscribe?hl=en . To unsubscribe from this group and all its topics, send an email to google-appengi...@**googlegroups.com. To post to this group, send email to google-a...@googlegroups.**com. Visit this group at http://groups.google.com/** group/google-appengine?hl=enhttp://groups.google.com/group/google-appengine?hl=en . For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out . -- You received this message because you are
Re: [google-appengine] Re: Error code 202
Was the internal issue resolved? We are experiencing the same problem with Java / HRD / app id - dev-electionear-d4-hrd Thanks, Dmitry On Thursday, March 8, 2012 9:51:37 AM UTC-8, Amy Unruh wrote: On Thu, Mar 8, 2012 at 8:40 AM, Amy Unruh amyu+...@google.comjavascript: wrote: For those of you seeing these errors, could you indicate whether you're using python or java, and whether you're using M/S or HRD? It would also be helpful to get your app ids, if you're willing to share them (you can email me directly if you like). Thanks to those who sent me more info. An internal issue has been filed, and it's being looked into. On Thu, Mar 8, 2012 at 8:08 AM, Tom Carchrae carc...@gmail.comjavascript: wrote: I'm getting these 202 errors also. It's driving me nuts. Most of the requests are relatively benign looking (request for a static image). Tom -- You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-a...@googlegroups.comjavascript: . To unsubscribe from this group, send email to google-appengi...@googlegroups.com javascript:. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en. -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[google-appengine] Looking to Host my site on google app engine
Hello Masters, I am very new and a non technical person. I want to host my site defensivedrivingcourseonline-texas.com on google app engine. Done required changes like adding CName but would not map my domain. Please help me in setting thing right. Thank You in advance. -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[google-appengine] Re: Disabling chunked transfer for blobstore requests
Hello Adrian, Have you find a way to disable chunked transfer for blobstore ? I have the same issue : I would like to know the total size of the file I am downloading so I could show a nice progress bar download indicator. Cheers, Erwann Le mercredi 7 avril 2010 04:28:56 UTC+2, Adrian Holovaty a écrit : Hi there, When Google App Engine serves media files from the Blobstore, it sends a Transfer-Encoding: chunked header and doesn't include a Content- Length header. This means a client downloading the file cannot do useful things such as displaying a progress bar, because the client doesn't know how large the file is until the whole thing is downloaded. My gut reaction upon seeing this was that Google was doing this for performance reasons, so that it didn't ever have to calculate the size of each blob... But, Google already *knows* the size -- it's accessible via Blobinfo.size for any given blob. In my particular case, I'd love App Engine to set Content-Length so I can display a download progress bar. I tried manually setting the Content-Length header (along with the magic X-AppEngine-BlobKey header) when serving a blob, but Content-Length was silently removed before it reached the client. So evidently App Engine is intentionally disallowing this. Is there any way to disable chunked transfer for blobs? Looks like somebody asked this in September 2008 but nobody responded: http://groups.google.com/group/google-appengine/browse_thread/thread/14c976299c032565/ If there isn't a way to accomplish this, I'd love to hear Google's reasoning, if only because it'd be interesting to hear why App Engine always uses Transfer-Encoding. Thanks, Adrian -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[google-appengine] issue on panorama image which have gpano xmp metada
Hi, We are working on panorama image, in this we are storing panorama image in google app engine. And this image will upload from mobile client, this image has gpano metadata.Actually this image will send to server, responsible of server is it have to save that pano image into google app engine. and my problem is storing image successfully but we are not retrieving full size image. using =s0 it giving error, but while using =s4000 working fine. so how do i get full size image which has gpano metadata.Other images like which doesn't have gpano metadata working fine. plz guide me.waiting for ur replay. Thank 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [google-appengine] [Python] Endpoints vs ProtoRPC ~200ms overhead
Hi Alex,
No, I don't think you're doing it wrong. Your post encouraged me to find
out the results of our internal analysis, which came up similar to what you
were seeing. The good news is that there are a few different efforts
underway to chip away at the latency total. I can't give specifics, but
this is something we're working to improve.
I wouldn't expect Endpoints to be as fast as ProtoRPC, but hopefully we can
close the gap a bit. I also hope that the extra features provided by
Endpoints (currently, or in the future) will make it worth the latency hit.
Thanks,
Dan
On Mon, Apr 15, 2013 at 2:49 PM, alex a...@cloudware.it wrote:
Hey, Dan. So, I basically took those numbers from logs of one of my
apps (Python 2.7, threadsafe=true, SDK v1.7.7)
I was looking at the logs the other day and noticed all Endpoints API
calls were taking at least 200ms up to 400-500ms (well, I clearly had
some Datastore and other stuff going on for it to be 500ms).
I started experimenting and ended up with those two simple classes,
EndpointsTest vs ProtoRpcTest, and TestMsg with the only msg string
field.
I then started calling their test method using curl (manually from a
terminal) and watch the logs, for maybe 15-20 mins repeatedly with
about 0.3-0.5 rps rate. I did the average in my head. Pretty easy - it
never went lower than 200ms and higher than 270ms for
EndpointsTest.test, and was in between 6ms-12ms for ProtoRpcTest.test.
This was running an app in EU datacenters. I thought I'd try it with
anothe app in US but got the same results.
Maybe I was doing it all wrong. Actually, I'll be happy to hear that.
Please let me know if this makes sense or I'm just comparing apples to
oranges.
On Mon, Apr 15, 2013 at 11:19 PM, Dan Holevoet
danielholev...@google.com wrote:
Hi Alex,
Can you share a bit more information about how you performed your tests?
Are
those numbers averages? How many times did you call both APIs? Was this
repeatable or did you run the test multiple times?
Thanks,
Dan
On Sat, Apr 13, 2013 at 1:46 AM, alex a...@cloudware.it wrote:
I'm not sure it's even possible (to reduce the overhead), and I do
understand there's another infrastructure layer that uses ProtoPRC lib,
but
still comare this:
@endpoints.api(name='test', version='v1')
class EndpointsTest(remote.Service):
@endpoints.method(VoidMessage, TestMsg)
def test(req):
return TestMsg(msg='Hello there')
curl /test/v1/test
{msg:'Hello there'}
- results in at least 200ms
to this:
class ProtoRpcTest(remote.Service):
@remote.method(VoidMessage, TestMsg)
def test(req):
return TestMsg(msg='Hello there')
curl -X POST /prototest.test
{msg:'Hello there'}
- results in about 7-10ms
There seem to be a few additional roundtrips going on when making
requests
via Endpoints.
Do you guys think it's possible to reduce the latency?
--
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
Dan Holevoet
Google Developer Relations
--
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
--
Dan Holevoet
Google Developer Relations
--
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
[google-appengine] Re: Sockets or Apple Push Notification support in Google App Engine
Well, thanks a lot for sharing this. If I don't recall incorrectly, apple's apns was accepting multiple push notification's at a time, and they were encouraging those push's to be sent in batches, I also remember reading that, if you push many items one by one, the calls were blocked. Anyone experienced in this area? I was thinking of building a simple pipeline system to build a custom push solution, but didn't do much research yet, recently implemented Parse's solution for apns. Appengine's socket introduction was surprising :) On Wednesday, April 17, 2013 11:41:31 PM UTC+3, GR wrote: Here's a sample project that can use sockets on App Engine to send out push notifications on ios: https://github.com/GarettRogers/appengine-apns-gcm On Monday, February 13, 2012 11:42:43 AM UTC-8, Giant Fighting Robot wrote: I have outgrown the 3rd party options for push notifications to Apple devices. I heard rumors that Google was planning to add socket support to the app engine which would enable me to roll my own push notifications. I'm starting to think that was Channels, which doesn't appear to do what I need. My questions are: 1) To double check, does the App Engine allow for apple push notifications without going through a 3rd party service? (maybe it was added in and I missed it?) 2) Assuming no, are there any plans to support it in the near future? I don't need a date, but if it's expected in the coming months I might grin and bear it until support comes, or if it's completely orthogonal to GAE's plans, I'd love to hear that so I can plan accordingly. -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[google-appengine] Re: Should I Implement the Search API?
We've been doing a fair amount of work with Search API lately. Some of the current challenges seem to be around operations aspects. E.g., we're trying to keep the search documents in sync with datastore entities. Because transactions don't extend across datastore and search indexes, they can get out of sync. So we occasionally need to look for orphaned search documents which means walking across them all and looking to datastore to see if the entity exists. This is very challenging given current quotas and something like the MapReduce library would be very, very helpful (specifically key-splitting / sharding) so that we could perform this operation in a smaller amount of time. j On Wednesday, 17 April 2013 13:59:10 UTC-6, Kaan Soral wrote: I haven't even considered reading the Search API documents up until yesterday, the production limitations of the Search API made me consider it as a non-existent feature. However it seems a lot of time has passed since it was first introduced and after reading the documents, I really really want to use it. Is there any ETA for scalable production usage? Will it ever reach a point that Total Index Size/API Calls will be able to reach TB's/Millions? Looking forward to hearing experiences/knowledge around Search Feature. -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[google-appengine] Re: Should I Implement the Search API?
Don't know if it would apply to your scenario but it might be a good idea to update search documents only when the datastore element changes significantly or gets removed. In my scenario syncing isn't an issue, however the document rank would change proportionally to the custom rank of the items, so the quotas are still worrying. On Thursday, April 18, 2013 1:08:05 AM UTC+3, Jason Collins wrote: We've been doing a fair amount of work with Search API lately. Some of the current challenges seem to be around operations aspects. E.g., we're trying to keep the search documents in sync with datastore entities. Because transactions don't extend across datastore and search indexes, they can get out of sync. So we occasionally need to look for orphaned search documents which means walking across them all and looking to datastore to see if the entity exists. This is very challenging given current quotas and something like the MapReduce library would be very, very helpful (specifically key-splitting / sharding) so that we could perform this operation in a smaller amount of time. j On Wednesday, 17 April 2013 13:59:10 UTC-6, Kaan Soral wrote: I haven't even considered reading the Search API documents up until yesterday, the production limitations of the Search API made me consider it as a non-existent feature. However it seems a lot of time has passed since it was first introduced and after reading the documents, I really really want to use it. Is there any ETA for scalable production usage? Will it ever reach a point that Total Index Size/API Calls will be able to reach TB's/Millions? Looking forward to hearing experiences/knowledge around Search Feature. -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[google-appengine] Google App engine looks down
Hi , My all apps running on Google App engine are behaving Odd, the Data is not being pulled from Datastore, instead it throws exception org.datanucleus.jdo.NucleusJDOHelper getJDOExceptionForNucleusException: Exception thrown Apps Status Dashboard shows that many service of Google are down today http://www.google.com/appsstatus#hl=env=statusts=1366203102143 and also it seems Google has scheduled its Maintenance today https://www.google.com/calendar/embed?src=4chlpo92ci2f54c2u21shbj...@group.calendar.google.comctz=America/Los_Angeles Please repsond to this and let us when this will be fixed. -- Thank you Satya -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[google-appengine] Re: Djangoform not supported anymore for python2.7, Any recommendation for replacement
djangoforms ModelForm is the same as the regular Django form class (django.forms.Form) but with additions that allow it to interact with datastore models. If you want to keep most of your form code and only have to update any of the GAE model specific stuff you do you can just include the latest Django library in your app.yaml and use the regular Django forms). I am in the process of doing this with one of our big apps. If you want to get rid of Django entirely in your Py27 version then WTForms is a good option but if you are happy with Django and don't want to re-write everything I recommend using the regular Django forms library. Best of luck. If you run into any gotchas along the way please share your solutions. And if you have particular questions I might know the answers as I am dealing with this now. - Bryce On Monday, April 15, 2013 2:14:06 PM UTC-7, Peter Chen wrote: Hi, I have a very large application hosted on google appengine which uses many djangoforms. Since now djangoform is not supported by google appengine anymore, I need to replace all of them, but I really don't want to, because there are so many of them. Is there any way I can put the djangoform back into my application? Peter -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[google-appengine] Re: Should I Implement the Search API?
Jason, Have you thought of using transactional tasks to update the search index? Or are you more concerned with concurrent updates to the same model? - Bryce On Wednesday, April 17, 2013 3:08:05 PM UTC-7, Jason Collins wrote: We've been doing a fair amount of work with Search API lately. Some of the current challenges seem to be around operations aspects. E.g., we're trying to keep the search documents in sync with datastore entities. Because transactions don't extend across datastore and search indexes, they can get out of sync. So we occasionally need to look for orphaned search documents which means walking across them all and looking to datastore to see if the entity exists. This is very challenging given current quotas and something like the MapReduce library would be very, very helpful (specifically key-splitting / sharding) so that we could perform this operation in a smaller amount of time. j On Wednesday, 17 April 2013 13:59:10 UTC-6, Kaan Soral wrote: I haven't even considered reading the Search API documents up until yesterday, the production limitations of the Search API made me consider it as a non-existent feature. However it seems a lot of time has passed since it was first introduced and after reading the documents, I really really want to use it. Is there any ETA for scalable production usage? Will it ever reach a point that Total Index Size/API Calls will be able to reach TB's/Millions? Looking forward to hearing experiences/knowledge around Search Feature. -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
