python-client | Python language bindings for Appium | Functional Testing library

I don't know about the Exchange Graph API, but EWS simply does not provide this information. Your best bet is the GetSearchableMailboxes service that you tried in exchangelib. EWS requires users to have the Discovery Management RBAC role for this to succeed.

Since you already have PowerShell commands that work for you, I would probably just call these commands from your Python script using a subprocess. Here's a blog post with some examples: https://www.phillipsj.net/posts/executing-powershell-from-python/

To answer your last question first:

The warning on top of the page refers to batch requests in general. This certainly includes whatever libraries you use, as long as they are using the same API (and of course, that's the case for the official Python library).

The blog post you mention is about discontinuing support for global batch endpoints, so that batch requests have to be API-specific from now on. That's totally unrelated to the current issues regarding Classroom API batch requests. It's also older than the warning, and is not taking those problems into account.

The documentation for pageSize doesn't specify the maximum value. For teachers.list and students.list mentions the default value (30). If you're setting a value higher than 30 and still returning only 30, chances are that's the maximum value too.

This doesn't seem to be documented, though:

pageSize: Maximum number of items to return. The default is 30 if unspecified or 0.

Beware, that doesn't seem to be the limit for courses.list (no default pageSize is mentioned, and a call to it retrieves way more than 30).

You cannot request multiple pages from a list request at once using batch requests, since you need the nextPageToken from the previous page to request the next page (using pageToken). That is to say, you have to make one request after the other.

It's a bug (harmless) in definition of the google provider 2.2.0 in fact:

In provider.yaml:

airflow.providers.google.common.hooks.leveldb.LevelDBHook

should be:

airflow.providers.google.leveldb.hooks.LevelDBHook

This was fixed in https://github.com/apache/airflow/pull/15453 and will be available in next version of google provider.

Why not approach C, :) a bit of both.

Both has pros and cons.

• A - use python to build ETL - pros - better control, flexible to do any logic you want. cons - you have to code in python and code in sql. If something fails, it will be a nightmare to do RCA. Maintenance may be harder in comparison. - performance wise, this approach will be poorer in case of huge volume of data.

• B - Use SQL to fetch data directly - pros - faster performance. less coding. cons - difficult to implement complex logic. Maintenance of code and schedule may be hard.

In addition to above, pls consider, your/teams comfort on python/SQL and future maintainability.
Currently we are using approach B in my cloudera project. We create views and then use insert to load final tables directly. We hardly need any UDF.
Now, my recommendation, please use approach B. And use approach A only in case you really can not create complex logic.

EDIT : Lets say, we have to load orders table. So we execute following blocks to load orders and dependent org,cust,prod tables.

It is possible to search for user by the external Id using the query parameter query.

1. Check the Python Quickstart
2. Use the method users.list
3. Define the customer. You can use my_customer
4. Define your query. Example: query = 'externalId:someValue'
5. Get the users that match the result of the list

When the server starts it shows you a list of available interfaces you can connect to, e.g.,:

No, it's not a sub folder.

When you create a bucket, you choose its name and the AWS Region to create it in. After you create a bucket, you can't change its name or Region.

Also, what you might find interesting, if you're using the AWS Console, that is shows all your buckets, in all regions, which might imply that S3 is a global service.

However, buckets exist in a specific region and you need to specify that region when you create a bucket.

Therefore, in minio, by location, they mean where you want to have your S3 backet end-point located. Full list of S3 service end-points is here.

So, basically, by setting location you get to choose where to "place" your bucket.

So I don't think its a surprise to anyone but Google's documentation is god awful. It's so scattered and the Python docs still reference their old depreciated library. Anyways.

So what I really needed to look at was this link "Enabling Server Side Access for your App". This is not linked to anywhere. Keep in mind this is entirely different than "Authenticating with a Backend Server"

This was a start. On the iOS side of things, we need to specify the server or backend's client_id.