I have installed the airflow 1.10.12 version using pip. However, I am not able to see the data profiling menu.
I checked my config file, and it's has secure_mode as false.
# If set to False enables some unsecure features like Charts and Ad Hoc Queries.
# In 2.0 will default to True.
secure_mode = False
do I need to do anything else?
The new RBAC Airflow UI (which is the only UI from 2.0.0) does not support Data Profiling or Ad-hoc Query:
https://github.com/apache/airflow/blob/master/UPDATING.md#breaking-changes
Due to security concerns, the new webserver will no longer support the features in the Data Profiling menu of old UI, including Ad Hoc Query, Charts, and Known Events.
Related
Is it possible to disable the airflow experimental API? I've searched through examples of airflow.cfg but didn't see anything there that would achieve it. Perhaps something can be done using auth_backend but I'm not sure what.
Since Airflow 1.10.11, the experimental API denies all requests by default (See PR).
If you are running an older version of Airflow, you can set
auth_backend = airflow.api.auth.backend.deny_all
Missing Data Profiling view when used FAB-Security with RBAC.
I have created users using airflow create_users
even the users have admin privileges data profiling view is not available on UI any Ideas?
As per the breaking changes section in Updating Airflow and backwards-incompatible the "new" webserver wont be supporting every feature of the old webserver.
Due to security concerns, the new webserver will no longer support the features in the Data Profiling menu of old UI, including Ad Hoc Query, Charts, and Known Events.
What's the best way to change the Firebase data model while you have multiple versions of your iOS app in production?
Since there's no 'application server' layer in the middle any changes in the database model could break older versions of the app.
Performance Related Example of the problem:
In version 1.0 I was naively keeping everything related to a post under '/posts/'. Now in version 2.0 I want to take Firebase's recommendation and add a '/user-post' endpoint to quickly list all posts for a given user.
People using version 1.0 of the iOS app are not writing any data to '/user-posts' since that endpoint didn't used to exist. People using version 2.0 therefore don't see any posts created by people using the old version of the app.
In theory I could create a server somewhere that listens for changes on '/post/' and adds them to '/user-posts' as well. That seems hard to maintain over time though if you have a lot of different versions of your app.
New Feature Example of the problem:
Lets say in version 1.0 of your mobile app you write new blog posts to '/posts/'. Now in version 2.0 of your app you introduce a Teams feature and all posts need to be in '/team/team-id/posts'.
People who haven't upgraded to version 2.0 will still be writing to '/posts'. Those posts won't be visible to people using version 2.0 who are reading from '/team/team-id/posts'.
I realize you could keep both endpoints simultaneously (and index /posts based on team ID) but over time this seems hard to maintain.
Traditional solutions:
If I were using something like Django or Express I'd do a database migration and then update the server-side endpoints for creating blogposts.
That would make changes in the database from the clients. I could in theory add an application-server tier to my architecture with Firebase, but that doesn't seem like it's recommended: https://firebase.googleblog.com/2013/03/where-does-firebase-fit-in-your-app.html
I would suggest you use Firebase Remote Config to show an alert via UIAlertController or different screen if an update is available. You could force the user to update to the current version and you don't have problems later because no posts with the old code can be created.
To answer your question:
I would develop a different app, add it to the same Firebase project and then let this app convert all old data to the new data model. So you would do this one time after releasing the new version and the old user data is converted to the new data model and everything works smoothly. You could also have a property like databaseVersion for every object.
To prevent future problems you could have a general property named app-version in your Firebase Realtime Database. Before every post the app checks if there is a newer version. If not the user can add the post but if there is a newer version you could show an message/alert via UIAlertController
I've created a WIX MSI that has 2 features (well actually more, but lets keep it simple for discussion). The first is a database feature that creates a db and runs some sql scripts. Another creates a web application in IIS. If the user is installing the db locally (local instance name), then I'd like to allow them to install SQL Server Advanced Services (need full text indexing) beforehand. If they're installing the web application, I'd like to make sure IIS is configured property (i.e. asp.net enabled).
I've been looking into bootstrapper, but I'm not sure how I marry this up with the feature selection, as the prerequisites appear to run before. I'd like the user to choose if they want to install the db, or the web application, or both. Because in some scenarios they would want them on different machines.
If they're only installing the db, then I don't want to enable IIS on the db machine.
-Lars
IMHO you don't need a bootstrapper at all. Use the two features that you already have and use conditions for the installation of your files / prerequisites, using the feature state / user selection in the feature tree.
According to Conditional Statement Syntax you can use the &feature-action in your conditions:
For example, the conditional expression "&MyFeature=3" evaluates to True only if MyFeature is changing from its current state to the state of being installed on the local computer, INSTALLSTATE_LOCAL.
does meteor have backend admin panel like "rais_admin" or "active admin" in rails for CRUD operations under models?
One of the teams at the first Meteor Summer Hackathon wrote the z-mongo-admin package that gives you a panel for basic CRUD operations. This should have the functionality that you're looking for.
Update 6/1/2015 - YES, since version 1.0.2. Once your app is running using meteor, run meteor shell in the same directory in a separate tab and you'll have a REPL.
Not yet. You can run meteor mongo in the app directory to access the database. Currently, you need the app running for this to work.
Observatory is a burgeoning logging and testing framework. Perhaps some kind of REPL will fit in the future.
Meteor Admin is an alternative to Houston based on the Autoform package.
It offers full CRUD based on your collection schemas.
Meteor Candy is an admin panel made just for Meteor. The idea is, everyone builds their Meteor app differently, but we do have commonalities such as the use of Accounts packages, etc, and that's a good place to start.
The package uses Dynamic Import available in Meteor 1.5, which means it adds virtually no weight to your client bundle.
Disclosure: I am the creator of the package
You should try Houston: https://github.com/gterrono/houston
Watch the video presentation here:
https://www.youtube.com/watch?v=8ASwWEZsAog