+1 (non-binding)
I could not found any more blocker issues. I ran all example dags and
some of our own dags via RBAC UI.
- feluelle
Am 19/01/2019 um 17:35 schrieb Kaxil Naik:
Hey all,
I have cut Airflow 1.10.2 RC3. This email is calling a vote on the release,
which will last for 72 hours. C
My vote is changed to 0 for this RC. I have prepared a pr to fix the viewer
issue(https://github.com/apache/airflow/pull/4569). @Deng Xiaodong
could you test the pr and see if the issue
still exists?
On Mon, Jan 21, 2019 at 11:05 AM Kaxil Naik wrote:
> @FengTao
>
> Do you have a "-1" vote or
@FengTao
Do you have a "-1" vote or "+1" vote?
On Mon, Jan 21, 2019, 18:21 Tao Feng Create a jira for the viewer bug(
> https://issues.apache.org/jira/browse/AIRFLOW-3745).
>
> On Mon, Jan 21, 2019 at 9:12 AM Deng Xiaodong wrote:
>
>> Hi Kaxil,
>>
>>
>> After double-checking, I believe the View
Create a jira for the viewer bug(
https://issues.apache.org/jira/browse/AIRFLOW-3745).
On Mon, Jan 21, 2019 at 9:12 AM Deng Xiaodong wrote:
> Hi Kaxil,
>
>
> After double-checking, I believe the Viewer access/permission issue is not
> a bug actually. Seems it's because the DAG-level access contr
Hi Kaxil,
After double-checking, I believe the Viewer access/permission issue is not
a bug actually. Seems it's because the DAG-level access control feature is
cherry-picked into 1.10.2rc3.
But my understanding is this feature is still under development? @feng-tao
kindly advise.
On the other
There is a PR improving the docs for the AWS connection right here
https://github.com/apache/airflow/pull/4514
(This may help people in the future)
-ash
> On 21 Jan 2019, at 15:15, Iván Robla Albarrán wrote:
>
> This resolve my problems
>
> Thanks!!!
>
> El lun., 21 ene. 2019 a las 15:35, D
This resolve my problems
Thanks!!!
El lun., 21 ene. 2019 a las 15:35, Deng Xiaodong ()
escribió:
> * “Extra Configuration”.
>
> You can find it in your connection edit page, the “Extra” section.
>
> XD
>
> On Mon, Jan 21, 2019 at 20:00 Deng Xiaodong wrote:
>
> > Hi Ivan,
> >
> > You can try to
Hi Ivan,
You can try to add your endpoint in extra confit of your connection, in
JSON format, like “{‘host’: ‘’}”.
XD
On Mon, Jan 21, 2019 at 19:48 Iván Robla Albarrán
wrote:
> Hi,
>
> We have our S3 installion (NO AWS)
>
> Could you help me, how i have to configure the conection? Where and h
* “Extra Configuration”.
You can find it in your connection edit page, the “Extra” section.
XD
On Mon, Jan 21, 2019 at 20:00 Deng Xiaodong wrote:
> Hi Ivan,
>
> You can try to add your endpoint in extra confit of your connection, in
> JSON format, like “{‘host’: ‘’}”.
>
>
> XD
>
> On Mon, Jan
Hi,
We have our S3 installion (NO AWS)
Could you help me, how i have to configure the conection? Where and how i
have to put the endpoint?
Always resolve the AWS endpoint
Thanks!!!
Regards,
Iván Robla
+1 (non-binding)
but it should be noted you have to run airflow initdb to get the super role
added; i keep forgetting to do that.
Cheers,
Josh
PXYData
On 2019/01/21 09:53:15, Naik Kaxil wrote:
> Hi XD,
>
> I could not replicate that in non-rbac UI but could replicate it on RBAC one.
>
> Pl
Yea this worked for me. I forgot you have to airflow initdb to create the
superuser field, may want to note that in the docs somewhere.
Cheers,
Josh
PXYData
On 2019/01/19 16:35:49, Kaxil Naik wrote:
> Hey all,>
>
> I have cut Airflow 1.10.2 RC3. This email is calling a vote on the
release,>
> wh
Hi XD,
I could not replicate that in non-rbac UI but could replicate it on RBAC one.
Please check this screenshot https://imgur.com/a/TgiQItO for non-RBAC
(Flask-Admin UI)
All the below issues don't seem to be a blocker for this release, however I am
open to views from all.
(1) Errors not sh
Hi XD,
I will test this and let you know.
One more bug cropped up https://issues.apache.org/jira/browse/AIRFLOW-3737 .
@fokko or someone with more K8s experience can have a look at it, please?
Regards,
Kaxil
On 21/01/2019, 09:05, "Deng Xiaodong" wrote:
Hi Kaxil,
I found anothe
Hi Kaxil,
I found another potential bug which is applicable for both RBAC and
non-RBAC UI:
Let’s say we’re trying to import a module which doesn’t exist at all, or
have any syntax error in the DAG, the DAG will not be parsed. In addition,
In earlier version, there will be a warning message appear
Hi Feng Tao,
As mentioned in my previous email to XD, as this is not a BLOCKER and the
fix exist as mentioned by Seelman, can you change your *vote back to +1 *.
And we can fix that in the upcoming release with other fixes which should
be quick and aim to release that in a month as well?
RBAC is
16 matches
Mail list logo
