[google-appengine] Re: so now there is SearchableModel, officially?
I was browsing around the documentation for the very same aim. What does this even mean? allowing multiple properties? It's been allowing multiple properties for a while to be indexed? The problem is that the cap on the indexing makes it impossible to use searchablemodel for entities that have more than around 300-400 words. (Which is most articles you'd ever want to make searchable). On Aug 7, 3:59 am, Kuber polo...@gmail.com wrote: In the python sdk 1.2.4 release note, i see this: Enhancement toSearchableModelallowing multiple properties to be indexed. Yes, we've heard about it for several months. But have google ever mentioned this thing in any official documentation before it's enhanced? Looking forward to google's documentation on it. --~--~-~--~~~---~--~~ 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-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: Too many indexed properties for entity
TextProperty and BlobProperty are ALREADY not indexed. So it doesn't make any difference. The problem with the searchable model is that it makes a few extra rows in your database that contains among other things a list of all the words that appear in your TextProperty. This means that it runs out of indexes and explodes and gives you the too many indexes error. There is no way around this. Its, unfortunately, a pitfall of the system. I think we can assume that Google is working on it. But nobody knows when it will be ready. It is likely that their database structure was not built for such large indexes. On May 12, 1:57 am, Ben bhym...@gmail.com wrote: I thought maybe the 1.2.2 update with the addition of indexed=false would solve this problem for me, but it doesn't seem to have any effect. I can move the title into a separate property is i mentioned above and that works ok, but i feel like i must be missing some other obvious solution here. my property is set like so: - class Item(search.SearchableModel): title = db.StringProperty(required=True) category = db.IntegerProperty() product = db.IntegerProperty() priority = db.IntegerProperty() description = db.TextProperty(indexed=False) contributors = db.StringProperty() - any ideas? On May 9, 12:20 am, 风笑雪 kea...@gmail.com wrote: SDK 1.2.2 can use indexed=False parameter on property constructor now. 2009/5/9 Ben bhym...@gmail.com I didn't figure out what was causing the problem, but i solved it by moving my Title string prop to a separate searchable class with a reference property, and leaving the description in a standard db model. might not work for everyone but solved my problem. thanks for the help. On May 8, 10:11 am, Devel63 danstic...@gmail.com wrote: You should be able to have a searchable TextProperty and a StringProperty. I do. If the advice below doesn't help, try posting your class definition here. On May 7, 10:27 am, ryan ryanb+appeng...@google.comryanb%2bappeng...@google.com wrote: http://code.google.com/appengine/docs/python/datastore/queriesandinde. .. describes this error. --~--~-~--~~~---~--~~ 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-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: iPhone cannot log in any more, system-wide issue, Google pls help
Possibly we should add the issue in the tracker... There currently is one but it has to do with a wrongly entered password and not with the login actually not working even if provided with correct credidentials... Everybody I know who is on app engine is facing this problem. On May 11, 12:16 pm, Pankaj Vishwani pankajvishw...@gmail.com wrote: I have been getting this for past two days too. Can someone please look into it since we are launching our website (www.wallpipe.com) on Monday (7:00pm PST). Thanks!! On May 10, 1:54 pm, mckoss mck...@gmail.com wrote: This is also failing with the Google Android browser (G1 phone). Didn't every Google employee get this phone for Christmas? Why has this fatal error in AppEngine persisted for over 36 hours? On May 9, 4:14 am, tijer troels...@gmail.com wrote: To reproduce the problem go to the google-developed app shell.appspot.com and try to login with aniphone. It not having aniphonethen spoof the useragent to theiphone(like with Safari 4's debug menu) and try logging in then. It fails with a 500-error page. What to do? This has been going on for two days now. It really sux when you're developing aniPhoneapplication :) --~--~-~--~~~---~--~~ 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-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: Sign In: Server Error - when using Android/T-Mobile G1
same error here on iphone. Spoofing the mobile useragent on a desktop browser is enough to reproduce error. Doesnt matter what application but try shell.appspot.com if you need to reproduce (to Google app engine staff) On May 9, 6:58 pm, mckoss mck...@gmail.com wrote: When I try to sign in to an AppEngine application OR even sign into Dashboard for my AppEngine app I get a 500 error. This seems to be specific to mobile browsers (it is NOT happening using desktop browsers). The error page after entering your Google credentials says: Error: Server Error The server encountered an error and could not complete your request. I first noticed this about 8am on May 9, 2009 - but it is still happening as of 10am. There is NO indication on the AppEngine status page that there are any problems, and I am not getting errors logged in my application when this happens. Until this is fixed, my mobile users cannot log in to their AppEngine applications. --~--~-~--~~~---~--~~ 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-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: Is anybody using indexed=False on properties? Is there a noticeable benefit?
Hi Kyle Yes I am using it and have been seeing a slight decrease in CPU consuption following the addition of indexed=False to around 15 string propertytypes and 3 list propertytypes in my two main model. It has reduced the load around 100ms or 12% or so. However, I must note that I have no way of actually scientifically monitoring this, other than really just looking at the average load before and after. It could also just be that the App Engine servers are running a little more smoothly. But I choose to believe that it at least had some effect. However, make sure you do not indexed=false ANY properties that you want to filter or sort on later, as this will ruin the backward- compatibility of your datastore model. Best, T On May 10, 4:19 pm, Kyle Jensen kljen...@gmail.com wrote: I have some models with many properties; however, I need indexes on only a handful. I noticed the new sdk supports indexed=False:http://code.google.com/p/googleappengine/wiki/SdkReleaseNotes Is anybody using indexed=False on properties? Is there a noticeable benefit? Sincerely, Kyle --~--~-~--~~~---~--~~ 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-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: Extreme amount of timeouts and other errors today
Yes certainly, the app id is rby. It is less of an issue now, but it was very bad btw 04-23 12:01AM and 04-23 04:50AM - and then before that btw 04-22 05:38AM and 04-22 07:59PM All times are given from the appviewer and is thus california time. I often get a lot of timeouts cluttered together for 4-5 hours at a time. It sucks very much when trying to build a professional and reliable site. I really hope you will manage to bring these errors down, or at least give a more specific error than timeout. I can force my app to try to re-do the query's and put's but I suspect that wouldn't do any real good in the long term. In the tracker I have recommended that you implement some sort of better explanation than timeout. If its because there are too many writes to the same entities then it should say that rather than timeout - and it should be possible for us to implement task queries that can then wait until its ok again to write and do it then. I have spent a lot of time using memcache to serve as a backend if the datastore fails - simply because it does that quite a lot. It shouldn't have to be like that, but I already spend a lot of time developing the site for GAE so obviously I would like to stay. However, if timeouts is going to continue to be something that just happens every hour or so on app engine, then I'm going to have to redevelop my app and go somewhere else with it. But then it would be proof that it'd be impossible to do anything serious on the platform and I sincerely hope it'll not develop into this direction. Anyway, a thumbs up for investigating the problem. I have profiled all I could and cached all I could, memcached all I could (maybe even a bit more than most would be comforable with doing). If there is anything at all I can do more then please let me know. On Apr 23, 8:20 pm, Jeff S (Google) j...@google.com wrote: Hi all, I've been investigating these issues. tijer and medecau, could you tell me the app IDs for these cases? Thank you, Jeff On Thu, Apr 23, 2009 at 8:25 AM, Ivan Maslov vanya@gmail.com wrote: Me too (id:topbestfriendshttp://appengine.google.com/dashboard?app_id=topbestfriends ) 2009/4/23 Henrik Berggren henrik.bergg...@gmail.com Having the exact same problem. pls help! On Apr 23, 11:07 am, tijer troels...@gmail.com wrote: There seems to be an extreme amount of timeouts and other errors today. My app is almost inaccessible... From the System Status I cannot see anything bout this situation, can somebody from Google please respond to the situation? --~--~-~--~~~---~--~~ 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-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: The new Google Analytics API and App Engine
Hi Jeff, I am using Python, and managed to get it to work by using the following. client = gdata.service.GDataService() # Tell the client that we are running in single user mode, and it should not # automatically try to associate the token with the current user then store # it in the datastore. gdata.alt.appengine.run_on_appengine(client, store_tokens=False, single_user_mode=True) client.email = MY_EMAIL_HERE client.password = NOT_FOR_YOUR_EYES # To request a ClientLogin token you must specify the desired service using # its service name. client.service = 'analytics' # Request a ClientLogin token, which will be placed in the client's # current_token member. client.ProgrammaticLogin() auth_key_for_analytics_to_use_in_header = client.current_token This lead me to believe that it's actually not the Auth-header that there's anything wrong with in the production environment, but rather picking up the correct Auth when utilizing app engine. However the above solved my problem, and I was able to get to the analytics api without an auth error. On Apr 22, 6:37 pm, Jeff S (Google) j...@google.com wrote: Hi tijer, I should be possible to set the authorization header. Are you using the Java runtime or Python. For Java, I looked at the gdata-java-client as an example (since you can use this library on App Engine) and it uses httpConn.setRequestProperty(name, value); Where httpConn is an HttpURLConnection. To set the Authorization header (this was in /trunk/java/src/com/google/gdata/client/http/HttpGDataRequest.java). If you feel like using the existing Java library for the Analytics API, a new download has just been released which includes convenience classes for this API. Happy coding, Jeff On Tue, Apr 21, 2009 at 6:32 PM, tijer troels...@gmail.com wrote: Hi, I'm trying to use the new Google Analytics API with App Engine. It works great on the development server locally, but as soon as I upload it to the production environment the authorization doesn't seem to go through. I callhttps://www.google.com/accounts/ClientLoginas specified in the api, then I pull the Auth= part and add it to an Authorization header that calls Google Analytics for a crosscut of data. It works in the development server, but when I do the same in the production environment I get the Auth= token from https://www.google.com/accounts/ClientLoginjust fine, but as soon as I call Analytics using the token I get an error that the Authorization did not come through. Is the Authorization header disabled in the production environment? Or how do I solve this problem? Thx --~--~-~--~~~---~--~~ 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-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: DataStore timeout
I am experiencing similar problems... I know AppEngine is still pretty young, but I don't understand the high amount of dropped connections and internal errors following these timeouts. Isn't the platform supposed to be scaleable? It doesn't seem very much so... My old mysql-database could pull much more, much faster, without dropping connections, under high load. On Apr 7, 4:20 am, campos huwen...@gmail.com wrote: I had the same problem since couple of days before. It all worked fine previously. My app has a somewhat high frequency, about 30 request/ sec. Is that the cause? How to solve it? On Apr 5, 3:56 pm, cc c...@gamegiants.net wrote: We are seeing the same issue today. No problem in the past. Somebody tweaked something! On Apr 3, 5:31 am, DarkCoiote darkcoi...@gmail.com wrote: Getting a bad number of datastore timeout... and the operation is 'simple', is a put in simple model;... Traceback (most recent call last): File /base/python_lib/versions/1/google/appengine/ext/webapp/ __init__.py, line 501, in __call__ handler.get(*groups) File /base/data/home/apps/naval-war/1.332510333196150921/main.py, line 218, in get person.put() File /base/python_lib/versions/1/google/appengine/ext/db/ __init__.py, line 669, in put return datastore.Put(self._entity) File /base/python_lib/versions/1/google/appengine/api/ datastore.py, line 166, in Put raise _ToDatastoreError(err) File /base/python_lib/versions/1/google/appengine/api/ datastore.py, line 1965, in _ToDatastoreError raise errors[err.application_error](err.error_detail) Timeout person model: class Person(db.Model): id = db.StringProperty() score = db.IntegerProperty(default=0) currentFleet = db.IntegerProperty(default=0) availableShots = db.IntegerProperty(default=0) maxShots = db.IntegerProperty(default=0) shipsSunk = db.ListProperty(int,verbose_name=Sunken ships list, default=[0,0,0,0,0]) shipsLost = db.ListProperty(int,verbose_name=Lost ships list, default=[0,0,0,0,0]) lastAccess = db.DateTimeProperty(auto_now_add=True) see... no references or anything complicated any tips on how to reduce the number of datastore timeouts?? --~--~-~--~~~---~--~~ 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-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: Can't access my application
Same problem for me, many of my users are complaining they see the same. It's been going on for more than 24 hours now. Google can you please fix this? There has been _a lot_ of outages the past month, it's not particularly credible for user-experience :( On 22 Mar., 07:56, Brandon Thomson gra...@gmail.com wrote: I fixed it temporarily by going to a neighbor's house for internet connection... but it is working on my original connection again now? I am confused what is the cause... On Mar 22, 2:13 am, WallyDD shaneb...@gmail.com wrote: Where do I get my membership badge? I have the same webpage :( On Mar 22, 2:00 am, William searchmon...@gmail.com wrote: I'm also getting this message on my app now. )-: On Mar 21, 5:14 am, Brandon Thomson gra...@gmail.com wrote: When I try to access my application I get the following message: We're sorry... ... but your query looks similar to automated requests from a computer virus or spyware application. To protect our users, we can't process your request right now. We'll restore your access as quickly as possible, so try again soon. In the meantime, if you suspect that your computer or network has been infected, you might want to run a virus checker or spyware remover to make sure that your systems are free of viruses and other spurious software. If you're continually receiving this error, you may be able to resolve the problem by deleting your Google cookie and revisiting Google. For browser-specific instructions, please consult your browser's online support center. If your entire network is affected, more information is available in the Google Web Search Help Center. We apologize for the inconvenience, and hope we'll see you again on Google. What is the cause and how can this be fixed? --~--~-~--~~~---~--~~ 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-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
