[google-appengine] Re: Python Conversion API Gone -- Now What ??
There are some Cloud services that through a HTTP API allow you to do conversions and/or OCR. On Monday, September 3, 2012 7:48:55 AM UTC-6, Sarvesh wrote: > > I was counting on the Conversion API for GAE hosted OCR. Too bad it is > being taken down. Is there a way I can avoid a separate hosting (CE/AWS > etc.) ? > > BTW here is what the Conversion Service link says: > Decommissioned! > > The Conversion API is being decommissioned. If you use the Conversion API > in your application, we strongly encourage you to find an alternative as > the API will be removed from the SDK and runtimes in November 2012. > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/Sljjed9BLcEJ. 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: Algae - Application Template for Google App Engine
Thanks for your contribution Liya! Have all the basics a modern web apps needs, including REST API's. On Tuesday, August 28, 2012 4:06:53 PM UTC-6, Ilya Bagrak wrote: > > While building Turn-O-Phrase (http://turn-o-phrase.com) and LinkPeelr ( > http://linkpeelr.appspot.com) on GAE, I realized that both applications > shared a lot of boilerplate code I was either reinventing from scratch or > copy pasting across. > > So for the last few months I've been working on a GAE application template > which I wish I had when I started tinkering with App Engine almost three > years ago. > > The result of this effort is Algae (http://green-algae.appspot.com), and > I am making it available to the app engine community at large. Algae > integrates de facto industry standards (like Twitter Bootstrap and HTML5 > Boilerplate) with features every web app needs (like user management and > third-party authentication). And that's just scratching the surface... > > I am sharing it in the hope that the developer community finds it useful, > and I welcome your feedback and pull requests. The code is here: > http://github.com/ibagrak/algae > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/1Td9Ye9plosJ. 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] Search API returns results twice when they meet more than one condition
I know that Search service is not stable enough, so this is just a kind of bug report. I've been playing with Search API. Looks amazing! But I noticed it return a record twice when it meet more than one search filter. For example: results = index.search( search.Query( query_string = '*(name:Christopher OR lastname:Ramirez)*', options = search.QueryOptions( limit=50, sort_options=search.SortOptions( expressions=[search.SortExpression( expression='name', default_value='')], limit=100) ) ) ) With th above code, records which match both filters (NAME and LASTNAME) will be returned twice. Also, Development SDK 1.6.6 throws an exception if a use a non ASCII char in the above filter string. The production enviroment didn't throw any error. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/jzmKJ3u-z34J. 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] Search API returns results twice when they meet more than one condition
I know that Search service is not stable enough, so this is just a kind of bug report. I've been playing with Search API. Looks amazing! But I noticed it return a record twice when it meet more than one search filter. For example: results = index.search( search.Query( query_string = '(name:Christopher AND lastname:Ramirez)', options = search.QueryOptions( limit=50, sort_options=search.SortOptions( expressions=[search.SortExpression( expression='name', default_value='')], limit=100) ) ) ) With th above code, records which match both filters (NAME and LASTNAME) will be returned twice. Also, Development SDK 1.6.6 throws an exception if a use a non ASCII char in the above filter string. The production enviroment didn't throw any error. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/5FDFHKjnAdEJ. 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: 1.7.0 Prerelease Now Available
Thanks Guido!
I addressed the issue thank to Alfred Fuller and Timh.
https://groups.google.com/forum/?hl=en&fromgroups#!topic/google-appengine/QL3in3ytY8U
The origin of the problem seems to be that some properties included in the
proyection were not indexed. And yes, you are right, I'm using db.
On Tuesday, June 19, 2012 2:03:23 PM UTC-6, Guido van Rossum wrote:
>
> On Tuesday, June 19, 2012 7:22:15 AM UTC-7, Christopher Ramírez wrote:
>>
>> On Monday, June 18, 2012 6:00:23 PM UTC-6, Marce (Google) wrote:
>>>
>>> - Projection queries are now supported in NDB.
>>>
>>
>> I have problems with projection queries. If I use them with
>> .order('-__key__').fetch(limit=20) records returned seems to be only the
>> even or odd ones. I opened a new discussion in this group but it was never
>> publicised.
>>
>
> To be clear, is this with NDB or with db? (I'm guessing db, since NDB
> doesn't support the syntax .order('-__key__') -- you'd have to use
> .order(-MyClass._key).
>
> Either way, can you please submit this to stackoverflow, with more details
> about what your code looks like and so on, so someone can help you?
>
> --Guido van Rossum
>
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-appengine/-/vwoN6F5a5WkJ.
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.
Re: [google-appengine] Projection Queries does not work with order() and Limit parameter
Thanks Alfred! Nice answare. Now that you point me "indexed" property, I remember I changed it for some fields included in the proyection. Some of them were not indexed before been in the proyection. So, that coud be the issue. On Wednesday, June 20, 2012 10:30:35 AM UTC-6, Alfred Fuller wrote: > > App Engine handles index building for you. When you add a new index, it > will re-index all entities. > > However, it is possible to save entities with an 'unindexed' property, > then change the model definition to save the same property but 'indexed.' > In this case, the old entities will remain unindexed, while new entities > will be indexed. The only way to fix this is to re-write the old entities > (as switching the indexing of a property is a schema change, and the > datastore does not manage your schema). > > On Wed, Jun 20, 2012 at 8:37 AM, Christopher Ramírez < > blindedbythed...@gmail.com> wrote: > >> No as I remember. >> >> How can I rebuild an Index? >> >> >> On Wednesday, June 20, 2012 2:53:12 AM UTC-6, timh wrote: >>> >>> >>> >>> >>>> I just added a few more records. The new ones appear without trouble. >>>> Missing records seems to be the ones saved before the projection index was >>>> created. >>>> >>>>> >>>>>>> >>> If you added a new index, then pre-existing items won't be in the index, >>> unless it's rebuilt. Did you add new properties when you added >>> the projection index ? >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "Google App Engine" group. >> To view this discussion on the web visit >> https://groups.google.com/d/msg/google-appengine/-/a6RsWljZlHYJ. >> >> 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. >> > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/eeTWsQev-f8J. 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.
Re: [google-appengine] Projection Queries does not work with order() and Limit parameter
No as I remember. How can I rebuild an Index? On Wednesday, June 20, 2012 2:53:12 AM UTC-6, timh wrote: > > > > >> I just added a few more records. The new ones appear without trouble. >> Missing records seems to be the ones saved before the projection index was >> created. >> >>> > > If you added a new index, then pre-existing items won't be in the index, > unless it's rebuilt. Did you add new properties when you added > the projection index ? > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/a6RsWljZlHYJ. 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.
Re: [google-appengine] Projection Queries does not work with order() and Limit parameter
Hello Tim!
I checked your the points.
> the missing records have values for the properties specified in the
> projection.
Yes, they have. I just even updated them in the datastore admin
(production) and still don't appear.
an index that hasn't been rebuilt
I ran appcfg.py update_indexed and the problem still persists.
Another problem is that I'm specifing a limit of 20 records, but the
projection query return me only 10 records. Actually, total existing
instances are 20
I just added a few more records. The new ones appear without trouble.
Missing records seems to be the ones saved before the projection index was
created.
On Tuesday, June 19, 2012 7:11:50 PM UTC-6, timh wrote:
>
> I haven't used projections in queries, but I was just reading the docs and
> noted the following about indexes.
>
> projectionList or tuple of names of properties to return. Only entities
> possessing the specified properties will be returned. If not specified,
> entire entities are returned by default. Projection
> queries<https://developers.google.com/appengine/docs/python/datastore/queries#Projection_Queries>
> are
> faster and cheaper than those that return complete entitites.
>
> *Note:* Specifying this parameter may change the query's index
> requirements.
> Maybe you have added the projection arg and are encountering an index that
> hasn't been rebuilt. That could be one explanation.
> The other thing to check would be if the missing records have values for
> the properties specified in the projection.
>
> Rgds
>
> T
>
> On Tuesday, June 19, 2012 10:35:32 PM UTC+8, Christopher Ramírez wrote:
>>
>> Yes it happens on both servers.
>>
>> On Monday, June 18, 2012 11:01:08 AM UTC-6, Alfred Fuller wrote:
>>>
>>> Does this happen in both the dev_appserver and production?
>>>
>>> On Fri, Jun 15, 2012 at 10:28 AM, Christopher Ramírez <
>>> blindedbythed...@gmail.com> wrote:
>>>
>>>> I was trying to use projection queries, but I had extrange issues using
>>>> them.
>>>>
>>>> I'm trying to use them like this:
>>>> offset_group = Clients.all( \
>>>> projection=('name', 'sex', 'birth_date', 'email', 'discount')
>>>> ).order('-__key__').fetch(limit=10, offset=skip_recs)
>>>>
>>>> The above code is supposed to bring me the last 10 clients. But
>>>> actually it does not return the last 10 (actually returns fewer and the
>>>> actual last record is not included). Also the results seems alternated or
>>>> maybe even/odd are skipped. If I take off projection param, the result is
>>>> as spected:
>>>> offset_group = Clients.all().order('-__key__').fetch(limit=10,
>>>> offset=skip_recs)
>>>>
>>>> I do not know if this is a bug in projection queries or they have to be
>>>> used in a different way. Please help me. I would like to use projection
>>>> queries because they are really fast!
>>>>
>>>> Kind Regards,
>>>> Christopher Ramírez
>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "Google App Engine" group.
>>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msg/google-appengine/-/Ahgw_iP_mukJ.
>>>> 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.
>>>>
>>>
>>>
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-appengine/-/FXLVSDojA1AJ.
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: HTML Website on Google App Engine
It's better for you to use python27 since it is multithreaded. That's means
an instance can handle more than one request simustaneously. Also increase
"default_expiration" when you be ready to deploy to the public your
website. default_expiration: "7d" (7 days) is a good value.
On Tuesday, June 19, 2012 3:48:10 AM UTC-6, Apra Barua wrote:
>
> Hey, I got it to work, it is not creating instance now. Thanks. The
> following app.yaml file worked.
>
> application: myappname
> version: 1
> runtime: python
> api_version: 1
>
> default_expiration: "12m"
>
> handlers:
> - url: /(.*\.(gif|png|jpg|ico|js|css|pdf|html))
> static_files: \1
> upload: (.*\.(gif|png|jpg|ico|js|css|pdf|html))
>
> - url: /
> static_files: index.html
> upload: index.html
>
>
> On Monday, June 18, 2012 10:08:32 PM UTC+5:30, Kyle Finley wrote:
>>
>> Have you mapped the root ('/') to a template? If so, App Engine will have
>> to start an instance to handle this request. Also any request that are not
>> specified in the app.yaml file will be sent to the instance causing it to
>> start up. Be sure to account map the *favicon.icon* for example.
>>
>> Generally I would not worry about it consuming frontend instance hours
>> unless your site is geting more then 1 or 2 request / sec. App Engine
>> graciously gives you 28hrs / day more then enough to fulfill 1 to 2 request
>> / sec.
>>
>> If you still have questions post your app.yaml file so we'll have a
>> better idea of your set up.
>>
>> - Kyle
>>
>>
>>
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-appengine/-/5sR8SAHUfGoJ.
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.
Re: [google-appengine] Re: 1.7.0 Prerelease Now Available
Thanks barry for pointing me that.
It's a recent answare. I opened the thread last week.
Also, I'm new to google groups and I dont't understand its GUI and
exploring methods quite well.
On Tuesday, June 19, 2012 8:26:40 AM UTC-6, barryhunter wrote:
>
> >
> > I have problems with projection queries. If I use them with
> > .order('-__key__').fetch(limit=20) records returned seems to be only the
> > even or odd ones. I opened a new discussion in this group but it was
> never
> > publicised.
>
> Umm, this one:
>
> https://groups.google.com/group/google-appengine/browse_thread/thread/40bde29f7cad63c5/e99aff23fe301802?hl=en&lnk=gst&q=Projection+Queries+does+not+work+with+order()+and+Limit+parameter#e99aff23fe301802
>
>
> You even have a reply from a Googler requesting more information.
>
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups
> > "Google App Engine" group.
> > To view this discussion on the web visit
> > https://groups.google.com/d/msg/google-appengine/-/hnghHKdho3IJ.
> >
> > 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.
>
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-appengine/-/J58CUcVnr0QJ.
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.
Re: [google-appengine] Projection Queries does not work with order() and Limit parameter
Yes it happens on both servers.
On Monday, June 18, 2012 11:01:08 AM UTC-6, Alfred Fuller wrote:
>
> Does this happen in both the dev_appserver and production?
>
> On Fri, Jun 15, 2012 at 10:28 AM, Christopher Ramírez <
> blindedbythed...@gmail.com> wrote:
>
>> I was trying to use projection queries, but I had extrange issues using
>> them.
>>
>> I'm trying to use them like this:
>> offset_group = Clients.all( \
>> projection=('name', 'sex', 'birth_date', 'email', 'discount')
>> ).order('-__key__').fetch(limit=10, offset=skip_recs)
>>
>> The above code is supposed to bring me the last 10 clients. But actually
>> it does not return the last 10 (actually returns fewer and the actual last
>> record is not included). Also the results seems alternated or maybe
>> even/odd are skipped. If I take off projection param, the result is as
>> spected:
>> offset_group = Clients.all().order('-__key__').fetch(limit=10,
>> offset=skip_recs)
>>
>> I do not know if this is a bug in projection queries or they have to be
>> used in a different way. Please help me. I would like to use projection
>> queries because they are really fast!
>>
>> Kind Regards,
>> Christopher Ramírez
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Google App Engine" group.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msg/google-appengine/-/Ahgw_iP_mukJ.
>> 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.
>>
>
>
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-appengine/-/_oXSMPD4KccJ.
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: 1.7.0 Prerelease Now Available
On Monday, June 18, 2012 6:00:23 PM UTC-6, Marce (Google) wrote:
>
> - Projection queries are now supported in NDB.
>
>
I have problems with projection queries. If I use them with
.order('-__key__').fetch(limit=20) records returned seems to be only the
even or odd ones. I opened a new discussion in this group but it was never
publicised.
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-appengine/-/hnghHKdho3IJ.
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] Projection Queries does not work with order() and Limit parameter
I was trying to use projection queries, but I had extrange issues using
them.
I'm trying to use them like this:
offset_group = Clients.all( \
projection=('name', 'sex', 'birth_date', 'email', 'discount')
).order('-__key__').fetch(limit=10, offset=skip_recs)
The above code is supposed to bring me the last 10 clients. But actually it
does not return the last 10 (actually returns fewer and the actual last
record is not included). Also the results seems alternated or maybe
even/odd are skipped. If I take off projection param, the result is as
spected:
offset_group = Clients.all().order('-__key__').fetch(limit=10,
offset=skip_recs)
I do not know if this is a bug in projection queries or they have to be
used in a different way. Please help me. I would like to use projection
queries because they are really fast!
Kind Regards,
Christopher Ramírez
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-appengine/-/Ahgw_iP_mukJ.
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.
