[google-appengine] Re: (Datastore)Creates indexes stuck in the [ Indexing ]!

After serval days indexes are still stuck. But I have solved the problem: 1. Use "gcloud datastore indexes cleanup" to delete the stuck indexes. 2. Recreate deleted indexes by "gcloud datastore indexes create". Riyalab瑞研網技 在 2020年11月20日 星期五上午11:00:29 [UTC+8] 的信中寫道： > When I deployed the java

[google-appengine] Re: Datastore not working nodejs.

Hello, To understand better, can you please provide more redacted details, error messages and timestamps? On Monday, November 2, 2020 at 4:54:03 AM UTC-5 schedule...@gmail.com wrote: > Hi, > > For past 3 to 4 hours I've been trying search answer for this. This looks > very odd. All the API

Re: [google-appengine] Re: Datastore emulator message type mismatch

Done. Thanks. On Tue, Oct 13, 2020 at 4:19 PM 'barrado' via Google App Engine < google-appengine@googlegroups.com> wrote: > Hi, > > I recommend you to post this question in StackOverflow > as it will have greater visibility and other > user might be able to help you.

[google-appengine] Re: Datastore emulator message type mismatch

Hi, I recommend you to post this question in StackOverflow as it will have greater visibility and other user might be able to help you. On Monday, October 12, 2020 at 4:50:17 PM UTC+2 Jagath Weerasinghe wrote: > Unfortunately, not much data shown with the added

[google-appengine] Re: Datastore emulator message type mismatch

Unfortunately, not much data shown with the added flags. $ gcloud beta emulators datastore start --log-http --verbosity=debug DEBUG: Running [gcloud.beta.emulators.datastore.start] with arguments: [--log-http: "true", --verbosity: "debug"] WARNING: Reusing existing data in

[google-appengine] Re: Datastore emulator message type mismatch

Could you retry the command with the --log-http and --verbosity=DEBUG wide flags enabled to see if it gives more information about the error? On Friday, October 9, 2020 at

[google-appengine] Re: Datastore in Remote Shell For Google App Engine (GAE) not working with zsh

Hello, I found this link here with the solution: There was an old dependency for the cryptography package that needed to be updated. Once I did that all was resolved, both

[google-appengine] Re: Datastore contention errors after switching from DB to NDB Cloud

Hello Remko, Just to clear any confusion, the product I was referring to was “Firestore in Datastore mode”. Although the names are similar, “Firestore” and “Firebase” are different in that “Firebase” is a development platform and “Firestore” is the new-generation of NoSQL Cloud Database. In

[google-appengine] Re: Datastore contention errors after switching from DB to NDB Cloud

Hi Pierre-Yves, Thanks for your comments. I'm aware of what causes contention errors, and how to resolve them. However, I'm just surprised that moving from the DB (*not* NDB) library to the Cloud NDB library suddenly causes contention errors. (and it's significant; e.g. a model that never used

[google-appengine] Re: Datastore contention errors after switching from DB to NDB Cloud

Hello Remko, Contention errors are usually observed when updating entities too rapidly, or when high read or write rates to lexicographically close documents. Since you recently changed the library to Cloud NDB, you may review this migration guide [1] which outlines key differences. One of

[google-appengine] Re: DataStore wont allow me to save byte[]

Thank you for reply, I found to save byte [] I had to wrap it as a Blob. On Friday, 17 May 2019 14:50:31 UTC+1, tonycavanagh1929 wrote: > > > I thought DataStore Allows you to save byte [], but I am getting an error > > [B is not a supported property type.]. I thought. datastore is supposed >

[google-appengine] Re: DataStore wont allow me to save byte[]

Hi again Tony, In fact, Byte string (short) and Byte string (long) are supported data types. You can gather more detail on the "Entities, Properties, and Keys" page . -- You

[google-appengine] Re: DataStore Key handling

We are on the same wavelength about updating entities, I think. For code samples, you could check the "Entities, Properties, and Keys" page . Your use-case is interesting, but does not require more detail to implement, than already

[google-appengine] Re: DataStore Key handling

But each case is a atomic, so to not recreate a key, I would need to store it somwhere mapped to a id. The idea is that the user sends CRUD operations via CRUD. For each object, I would just pass an ID. And Id is diiferent to a key. So on each new call to the datastore to say update an entity.

[google-appengine] Re: DataStore Key handling

Hi Tony, In fact, the reply looks somewhat different: once the key was created when you created the entity, you use it to retrieve the entity information whenever needed, so you don't need to recreate this key each time you want to access Datastore: you just reuse it. -- You received this

[google-appengine] Re: DataStore Key handling

Thank you for replying I understand what the key is, My question was that I have to recreate it every time I want to access the DataSotore. I guess I have to, On Friday, 17 May 2019 08:53:12 UTC+1, tonycavanagh1929 wrote: > > Every Time I wish to carry out any CRUD operation on a datastore, I

[google-appengine] Re: DataStore Key handling

Hello Tony, Each entity in Datastore has a key that uniquely identifies it. The key consists of the following components: - The namespace of the entity, which allows for multitenancy - The kind of the entity, which categorizes it for the purpose of queries - An identifier for the individual

[google-appengine] Re: Datastore Admin

Hello Rajesh, You can still enjoy the old functionality; you are in the same time encouraged to use similar functionality from the Managed Export and Import Service . Related information is to be found on the "Datastore Admin

[google-appengine] Re: Datastore export permission only

Hello, Engineers are aware of the request and there is no ETA at this moment. You can follow the progress of this feature request by following this link . You can “star” it so to receive notification on any updates on this request. On Wednesday,

Re: [google-appengine] Re: Datastore export permission only

Hi Dan McGrath, When will this feature be released? Rajesh *www.GainERP.com * *Field Service Software on Google Cloud Platform and Mobile* On Thu, Dec 20, 2018 at 12:01 PM Rajesh Gupta < rajesh.gu...@veersoftsolutions.com> wrote: > Appreciate your reply. Hope to see

Re: [google-appengine] Re: Datastore export permission only

Appreciate your reply. Hope to see the feature soon. On Wed, Dec 19, 2018 at 12:48 AM 'Dan McGrath' via Google App Engine < google-appengine@googlegroups.com> wrote: > Thanks for the feedback Rajesh. I'm the product manager for Cloud > Datastore, and want to note we agree with you. We're

Re: [google-appengine] Re: Datastore export permission only

Thanks for the feedback Rajesh. I'm the product manager for Cloud Datastore, and want to note we agree with you. We're working through some implementation details for custom roles at the moment, and unfortunately don't have dates to share. It's definitely in our plans to make this available

Re: [google-appengine] Re: Datastore export permission only

It is risky to give the comple datastore.importExportAdmin for upcoming or new engineers. Even experienced engineer can make a mistake importing instead of exporting. When is the permission “datastore.databases.export” supported for the custom roles. Rajesh *www.GainERP.com

[google-appengine] Re: Datastore export permission only

Hello Rajesh, Thank you for the message. Usually by creating a custom role certain permission can be assigned to users. You can get more details about IAM custom role here

[google-appengine] Re: Datastore export permission only

any idea on how to setup a user with only datastore.databased.export permission? On Wed, Dec 12, 2018 at 7:40 PM Rajesh Gupta < rajesh.gu...@veersoftsolutions.com> wrote: > Hello, > I am setting up a new user in the IAM. > I want only the datastore.databases.export permission. > > I don't want

Re: [google-appengine] Re: Datastore & Firestore Transaction

Users who are looking to architect existing datastore app and still want to benefit from the firestore native mode, please star this issue. I am requesting some kind of cross database transaction or something that existing apps can write to both datastore as well as firestore native more reliable.

Re: [google-appengine] Re: Datastore & Firestore Transaction

Hi Rajesh, I can understand that you have a concern moving forward with Firestore as you have been using App Engine with Datastore for such a long time. I am providing you a link to the documentation which addresses the process of automatic upgrade of Cloud Datastore to Cloud Firestore

Re: [google-appengine] Re: Datastore & Firestore Transaction

Hi Rajesh, I can understabd that you have a concern moving forward with Firestore as you ahve been using App Engine with Datastore for such a long time. I am providing you a link to the documentation which addresses the process of automatic upgrade of Cloud Datastore to Cloud Firestore

Re: [google-appengine] Re: Datastore & Firestore Transaction

I have an appengine app running for 6-7years. what is the best way going forward to take advantage of the firestore native mode. I understand some of the limitations of the datastore are removed, when the datastore is moved into 'firestore datastore mode'. Request the team to provide firestore

[google-appengine] Re: Datastore & Firestore Transaction

You cannot use Cloud Firestore and Cloud Datastore at the same time in Google Cloud Platform. To use Cloud Firestore database, you need to choose one of two modes, Native mode or Datastore mode. Depending on your requirements, you need to choose one of it. As you specifically aiming to get

[google-appengine] Re: Datastore & Firestore Transaction

We are more & more thinking on how to take the benefit of firestore in existing appengine applications. Existing appengine applications can greatly benefit with some kind of guaranteed cross database transactions On Fri, Oct 12, 2018 at 9:25 AM Rajesh Gupta < rajesh.gu...@veersoftsolutions.com>

Re: [google-appengine] Re: Datastore - Audit Log of the Project Owner

Hi,   Thanks for the assistance. I really hope that the feature will be easy to implement because it is the only way our project can comply with the current accounting standards. Regards, Dzhovani On 9/17/2018 7:32 PM, 'Julie (cloud platform support)' via Google App Engine wrote: The

[google-appengine] Re: Datastore - Audit Log of the Project Owner

The Datastore team is aware of this request and is currently looking into it. You can use this issue tracker[1] to track the progress of that feature request. Please note that feature requests are not guaranteed to fulfilled and there is no ETA on them. [1]

[google-appengine] Re: Datastore - Audit Log of the Project Owner

So to clarify, you want a feature for audit logs to record the email addresses of users why they modify Datastore data? Can you post a screenshot of the Audit logs that do not currently contain this as it is not clear where you would like this implemented after removing all personal and

[google-appengine] Re: Datastore and Memcache access errors from today

Greetings. I'm back to getting hundreds of Datastore and Memcache errors. I'll try redeploying, but can anyone please look into it? On Tuesday, January 30, 2018 at 11:54:38 PM UTC+2, Gabriel Axel wrote: > > I redeployed half an hour ago and got no exceptions since then. Thanks. > > On Tuesday,

[google-appengine] Re: Datastore and Memcache access errors from today

I redeployed half an hour ago and got no exceptions since then. Thanks. On Tuesday, January 30, 2018 at 10:25:36 PM UTC+2, Kenworth (Google Cloud Platform) wrote: > > QQ: What happens if you try to redeploy your code (same code, just re-ran > deployment)? > -- You received this message

[google-appengine] Re: Datastore and Memcache access errors from today

Hi Gabriel, what happens if you try to redeploy your code (same code, just re-ran deployment)? -- 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] Re: Datastore storage size

It may be worthwhile mentioning here that, even if Datastore scales it's size automatically, one can prevent incurring costs due to extreme scaling. It is possible to set a spending limit for your project. This is documented in the "Quotas and Billing" sub-chapter of the "Sign up" page

[google-appengine] Re: Datastore storage size

Hello John, Cloud Datastore automatically scales its size up or down, you don't need to change anything. The pie chart is showing the size for each resource (as shown in the table on its right) relative to the total size currently taken by this datastore. If you hover over the colored

[google-appengine] Re: Datastore on flex nodejs appengine isn't working

Hi Tony I have the same issue, did you find a way to solve it? On Wednesday, February 1, 2017 at 4:16:00 PM UTC+2, Tony Stark wrote: > > Since yesterday does not work datastore through the flex evironment. > Application just not receives the response from the datastore. If I run the >

[google-appengine] Re: Datastore: Problem updating entities

You can view the Python example which is importing these datastore libraries . For further

[google-appengine] Re: Datastore: Problem updating entities

Hi Shivam, Is it possible to use Python instead of Java on Dataflow to do the update on Datastore? If so where can I find an example? Best regards, On Tuesday, 15 August 2017 18:04:58 UTC+1, Shivam(Google Cloud Support) wrote: > > The job could tend to be slow for such amount of entities

[google-appengine] Re: Datastore: Problem updating entities

The job could tend to be slow for such amount of entities following the example here . The solution for proper Datastore Map Reduce solution in the cloud would be Datastore I/O using Dataflow

[google-appengine] Re: Datastore: Problem updating entities

The job was actually doing slightly more than just setting a property to a default value, it also was doing a .strip() in one of the fields due to an error in our insert scripts, so in some cases there is a need to do a mass update on all entities, it definitely doesn't happen often but we

[google-appengine] Re: Datastore "checkNotNull" Error

A thread like this is off-topic for Google Groups, and should be posted to StackOverflow . While I'd like to help you, this isn't the place to do it. This forum isn't meant for specific 1-on-1 technical issues, but for general

[google-appengine] Re: Datastore: Problem updating entities

There should be no actual need to mass-put a new property to all of your entities, and set that new property to a default value since the Datastore supports entities with and without set property values (as you have noticed with the failed Map Reduce job). You can assume that if an entity

[google-appengine] Re: Datastore structure for app like Google Forms?

Very interesting idea. Many thanks for your detailed answer! On Wednesday, August 2, 2017 at 6:05:59 PM UTC+1, Jordan (Cloud Platform Support) wrote: > > There does not seem to be any limit for Datastore Kinds > . Essentially > you would

[google-appengine] Re: Datastore structure for app like Google Forms?

Essentially you would have one 'Form' Kind. When someone creates a new main Form entity via your application you then make that main Form available to other user's via your application. When a user fills out the main Form via your application, you then save a copy of that Form entity for that

Re: [google-appengine] Re: Datastore Internal Error

Hello Josh, Is this issue still open, we have many services raising this error today and yesterday. This is happening with get/put/fetch calls. We are not sure what all data is lost or what needs to be done to control this. I don't see any status update on https://status.cloud.google.com/.

[google-appengine] Re: Datastore small operations daily quota

George, The issue was not with keys more than 1000 (in fact we have fewer than 1000 entities). The issue was with over quota of small operations (throwing over quota error). The document says small operations (keys only queries) are unlimited but in my project it was showing over quota (5

[google-appengine] Re: Datastore small operations daily quota

Unfortunately I don't enjoy sufficient permissions to access the screen you copied in your message, and check the situation. The "Keys-only queries" paragraph of the "Datastore Queries" document recommends to limit GetAll

[google-appengine] Re: Datastore small operations daily quota

George, I have sent a private message to you with my project number. Could you please let me know what the issue was? How do I circumvent this issue going forward? thanks, dhanunjay On Tuesday, May 16, 2017 at 10:58:07 PM UTC+5:30, George (Cloud Platform Support) wrote: > > The issue seems

Re: [google-appengine] Re: Datastore small operations daily quota

George, Here is the project number: 91872220893 thanks, dhanunjay On Tue, May 16, 2017 at 10:58 PM 'George (Cloud Platform Support)' via Google App Engine wrote: > The issue seems to be triggered by a particular situation related to your > project's

[google-appengine] Re: Datastore small operations daily quota

The issue seems to be triggered by a particular situation related to your project's settings. You are most welcome to send me a private message via the drop-down menu of the reply button, right-top, with your project number. Any other details you deem of consequence may prove helpful as well.

[google-appengine] Re: Datastore queries are unpredictably slow when a limit is applied

Thanks for your help. Adding the index worked out for us. Thank you for providing the other suggestions as well. -- 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

[google-appengine] Re: Datastore queries are unpredictably slow when a limit is applied

Datastore query times are not guaranteed to be consistent, as Datastore is a shared, distributed service. Since you're performing 4 equality filters this can add to the variation. The question of how to optimize for speed is a bit broad and depends on your data model. With that being said I

[google-appengine] Re: Datastore String length limit of 1,500 bytes when using JDO

There's no special JDO extension for Datastore that will automatically treat a String as Text, unfortunately. Even if there was, setting 'unindexed' for a String property wouldn't be a big enough hint to treat it as Text, because there's still a difference in Datastore between an unindexed

[google-appengine] Re: Datastore queries are unpredictably slow when a limit is applied

My replies take a long time to get posted here since I'm new. My application is written in Java and instance class of my app is F4. There are a total of 922,758 entities of that Kind in the Datastore. Here's the function: public static Map getEntitiesUsingQueryCursor( String kind , int

[google-appengine] Re: Datastore queries are unpredictably slow when a limit is applied

Additional info: The query has 4 "equals" filters on 4 different properties (3 strings and 1 Boolean). It does not have a sort order applied. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop

[google-appengine] Re: Datastore queries are unpredictably slow when a limit is applied

Can you let us know what language runtime you're using, preferably with a sample of code which shows your query and fetch options? On Saturday, March 4, 2017 at 12:01:57 PM UTC-5, Arjunkumar Udainath wrote: > > I have an app that's sort of like a to-do application. Any given user > would have

[google-appengine] Re: Datastore String length limit of 1,500 bytes when using JDO

Nick, When I'm using the Datastore Console to manually update the table it will throw an error related to the index if I have the indexing turned on for the field and try to store a large value. When I turn indexing off I am able to store large strings through the console. In my Java/JDO

[google-appengine] Re: Datastore String length limit of 1,500 bytes when using JDO

Hey Jim, Do I understand correctly that you only see the issue when you attempt to index the field - or what's the same thing - it doesn't occur when you turn the field's indexing off? Cheers, Nick Cloud Platform Community Support On Thursday, March 2, 2017 at 1:26:02 PM UTC-5, Jim wrote: >

[google-appengine] Re: Datastore connection problem

You'd want to ensure that you are correctly setting the emulator environment variables with $(gcloud beta emulators datastore env-init) after starting it according to the docs , however even when I do that the bookshelf sample

Re: [google-appengine] Re: Datastore Internal Error

This was a known issue. We will be following up with an incident report which will be posted on the Cloud Status Dashboard and cover all occurrences of this issue on 2017-02-14. On Wed, Feb 15, 2017 at 8:14 AM, Marcel Manz

[google-appengine] Re: Datastore Internal Error

Hi Vinod, In case this is still happening, I will need you to provide me with the following information in order to help you further: - The Cloud SDK version you are using. - A minimal working example of your code demonstrating this issue. Let me know if you would prefer to be

[google-appengine] Re: Datastore: how to design for huge time-series data

I would recommend using the BigQuery streaming API. We do a heck of a lot of that at Bluecore and it works well. Depending on how your data arrives, you may want to use a Task Queue or similar to collect lots of rows together to be able to insert batches into BigQuery, which will be more

[google-appengine] Re: Datastore: how to design for huge time-series data

Hey Etienne, You've correctly enumerated a few ways to transfer data from Cloud SQL to BigQuery: * export to CSV and load the CSV into BigQuery * retrieve the data with an app and stream it into the BigQuery API * export to Datastore and then import to BigQuery There are also other ways,

[google-appengine] Re: Datastore: how to design for huge time-series data

Hi, Sorry for the repeat, but I am trying to wrap my head around the GAE-osphere and I am getting a bit confused; I need to store and retrieve/analyse timeseries data, of varying sizes and resolutions; at the moment, the data is received and stored on GAE through to Google Cloud SQL (python).

[google-appengine] Re: Datastore on flex nodejs appengine isn't working

While this is important, I would recommend filing an issue on the App Engine public issue tracker as that seems like a more appropriate forum for such a report. This discussion group is generally better suited for exchanging best

[google-appengine] Re: Datastore query

Hey Yair, The less secure way to allow your Android client to query your Datastore would be to directly allow the client access using the Datastore Client Library . By using the Client Library directly

[google-appengine] Re: Datastore query

Thank you Jordan for the fast response. What you are offering is regardless of the servlet module I deployed to app engine ( which writes to datastore ) ? There is no other way than Endpoints, for datastore query ? On Monday, January 2, 2017 at 9:54:44 PM UTC+2, Jordan (Cloud Platform Support)

[google-appengine] Re: Datastore query

To allow external clients to perform a read operation on your Google Cloud project's Datastore, you will need to expose an App Engine Endpoint . Simply create an App Engine method that performs the Datastore query

[google-appengine] Re: Datastore query

Welcome, Yair, You wrote your own servlet that is able to write data to Datastore? Is there some snippet of code you can post here to make it clear where you're stuck? Are you using Datastore API from App Engine SDK directly or are you using some framework? On Monday, January 2, 2017 at

[google-appengine] Re: Datastore get_or_insert in Java

You can achieve the same 'fetch or create' entity functionality in Java using a simple 'try/catch' block . This is essentially the same way

[google-appengine] Re: Datastore

We'll need more details about what you're trying to do in order to help. Are you following any specific documentation? On Saturday, November 26, 2016 at 12:01:43 PM UTC-5, Ottavio Migliaccio wrote: > > Hi, > I use Android study. > Insert correctly the entities in the datastore, but when I turn

[google-appengine] Re: Datastore index stuck

(A link to the Public Issue Tracker for future reference) On Monday, August 22, 2016 at 4:13:22 PM UTC-4, Nick (Cloud Platform Support) wrote: > > Hey Joshua, > > This appears like it might be best reported in the Public Issue Tracker. >

[google-appengine] Re: Datastore index stuck

Hey Joshua, This appears like it might be best reported in the Public Issue Tracker. No matter, since it's here now, and if you send me your project ID and the details of the index via direct email I'll be glad to look into what we can see and report back. Cheers, Nick Cloud Platform

[google-appengine] Re: Datastore field formats

> > >> @Vitaly : how can I use db.TextProperty in the example I gave ? because >> it was not obvious for me, i've tried a lot >> > > > https://cloud.google.com/appengine/docs/python/datastore/typesandpropertyclasses#Text > > if your json is really BIG, maybe you need zip it and save to

[google-appengine] Re: Datastore field formats

> > > @Vitaly : how can I use db.TextProperty in the example I gave ? because it > was not obvious for me, i've tried a lot > https://cloud.google.com/appengine/docs/python/datastore/typesandpropertyclasses#Text -- You received this message because you are subscribed to the Google Groups

[google-appengine] Re: Datastore field formats

great Clement! @Vitaly : how can I use db.TextProperty in the example I gave ? because it was not obvious for me, i've tried a lot On Wednesday, July 27, 2016 at 9:39:37 PM UTC+2, Vitaly Bogomolov wrote: > > Hi, All. > > >> in Datastore, long strings (larger than 1500 bytes) cannot be indexed (

[google-appengine] Re: Datastore field formats

Hi, All. > in Datastore, long strings (larger than 1500 bytes) cannot be indexed ( > https://cloud.google.com/datastore/docs/concepts/entities#text_string) > The issue here is that, by default, Datastore tries to index every > property you give it, unless told otherwise. > > Here, it tries to

[google-appengine] Re: Datastore field formats

Hi Christopher, in Datastore, long strings (larger than 1500 bytes) cannot be indexed (https://cloud.google.com/datastore/docs/concepts/entities#text_string) The issue here is that, by default, Datastore tries to index every property you give it, unless told otherwise. Here, it tries to index

[google-appengine] Re: Datastore read costs for nil entities

> > I am working on optimizing datastore calls, and saw that the cost of > datastore read calls is 6 cents per 100,000 entities worth of reads. If I > do a datastore.Get call for an entity that isn't in the datastore, does > that count as a datastore read, or is it only considered a datastore

[google-appengine] Re: Datastore Statistics: Is history ever still available?

It looks like the documentation is out of date, and there's been an issue filed to have it updated. Indeed, there is only one instance of __Stat_Total__, and the recommendation is to just fetch 1 entity and retry if no entities were returned. On Monday, July 11, 2016 at 11:49:45 AM UTC-4, Evan

[google-appengine] Re: Datastore Writes being Disabled

You may want to star the relevant public issue . This was originally reported for editing custom domain mappings, but it looks like the problem may be generally related to the project selector and can cause issues on other

[google-appengine] Re: Datastore Writes being Disabled

Yeah it was between switching projects I believe. I don't think that writes were actually disabled, and it eventually stopped the message. On Monday, May 23, 2016 at 3:05:57 PM UTC-5, Adam (Cloud Platform Support) wrote: > > Was this noticed after switching projects using the drop-down? Does

[google-appengine] Re: Datastore Writes being Disabled

Was this noticed after switching projects using the drop-down? Does re-enabling writes persist after first refreshing the page? We've noticed the project selector causing stale data from the previous project to be displayed in some cases, but a page refresh will update it correctly. On Friday,

[google-appengine] Re: Datastore Writes being Disabled

I'm getting that too on one of my projects! I re-enable writes and then it just gets disabled again. On Thursday, May 19, 2016 at 8:23:42 PM UTC-4, Daniel Young wrote: > > I've gone into the Datastore Console and it seems the writes are being > disabled automatically (or a message is being

Re: [google-appengine] Re: Datastore Admin stopped working

Thanks for your support Adam, I have posted the issue. Michael On Tuesday, May 3, 2016 at 12:06:26 AM UTC+2, Adam (Cloud Platform Support) wrote: > > I see this too. The Datastore Admin has a dependency on the old builtin > mapreduce library which can't be enabled anymore. It does not work

Re: [google-appengine] Re: Datastore Admin stopped working

I see this too. The Datastore Admin has a dependency on the old builtin mapreduce library which can't be enabled anymore. It does not work with the latest appengine-mapreduce library even when fixing the handler paths (/mapreduce -> /_ah/mapreduce) in the include.yaml. Vendoring the old

[google-appengine] Re: DataStore Composite index is created, but there are no entries & when the query is run null result is coming though there are valid entries for the query in the datastore

Hey Venkata, This sort of question should be asked over at Stack Overflow . This forum is meant for more high level discussion of the platform and services, rather than specific-issue technical support. We also monitor Stack Overflow, and it has the benefit of being

Re: [google-appengine] Re: Datastore Admin stopped working

Hi Adam, hi Josh, thanks for your help. We've deployed the new version according to your suggestions and the Datastore Admin works fine again. Still, we can not do any backups. Mapreduce gets kicked off (in the logs of the new datastore version we see

Re: [google-appengine] Re: Datastore Admin stopped working

Also, regarding the inconsistencies in the console for 'ah-builtin-python-bundle', feel free to post to the issue tracker so we can grab the app ID and investigate the specific project. On Saturday, April 30, 2016 at 2:53:36 PM UTC-4,

Re: [google-appengine] Re: Datastore Admin stopped working

Thanks Josh, I didn't think the source for this was available as 'appcfg.py download_app' is purposely blocked for 'ah-builtin-python-bundle', but it was right in the SDK all along! Although restoring to 'ah-builtin-python-bundle' won't work due to 'ah-builtin' being a reserved version name

Re: [google-appengine] Re: Datastore Admin stopped working

For anyone who is or has been affected by an accidental deletion of datastore admin, a workaround is to deploy datastore admin as a separate version or module of your app. The code for datastore admin is provided in the Cloud SDK: $CLOUD_SDK_PATH/google/appengine/ext/datastore_admin On Fri,

[google-appengine] Re: Datastore Admin stopped working

Adam, unfortunately the 'ah-builtin-python-bundle' is visible under 'Versions'. At least it was visible for me in the afternoon - now it disappeared again. I can provide you with a screenshot if you like. From my perspective this looks like a bug in Console. Cheers Michael On Wednesday,

[google-appengine] Re: Datastore Admin stopped working

Adam, since this is a required version for administering our applications, can Google put in safeties to prevent it from being deleted? It's pretty scary that it can accidently be deleted and not be re-created. thanks, christian -- You received this message because you are subscribed to

[google-appengine] Re: Datastore Admin stopped working

We only used the Cloud Console for deleting the versions. We had a lot of versions so we used the select all checkbox and then deselected the versions we are still using. We are not sure if the version 'ah-builtin-python-bundle' was in there, but it was deleted during the same time according

[google-appengine] Re: Datastore Admin stopped working

If this had happened, there isn't a way to redeploy this version or download it from another project unfortunately. You would need to recreate the project. Although 'ah-builtin-python-bundle' isn't visible in the console under 'Versions', it's still possible to delete using appcfg.py, so

[google-appengine] Re: Datastore admin is unable to delete entities

We've seen this happen when the 'default' task queue has the 'target' overridden in queue.yaml / queue.xml, so that the push tasks needed for the mapreduce jobs are not executing on the default module for 'ah-builtin-python-bundle' but on some other, possibly invalid module / version. I'd

  1   2   3   4   5   6   7   8   9   10   >