404 Not Found for `EmptyOperator` docs for version 2.7+

[jroachgolf84]

What do you see as an issue?

When attempting to navigate to the following link for the EmptyOperator (https://airflow.apache.org/docs/apache-airflow/3.0.2/_api/airflow/operators/empty/index.html) for version 2.7+, the following message is shown:

404 Not Found

Code: NoSuchKey
Message: The specified key does not exist.
Key: docs/apache-airflow/3.0.1/_api/airflow/operators/empty/index.html
RequestId: Y8G1RYQZ17G9YCFJ
HostId: KOVclWKSICirfLsvC1fpVRJBWQ8S030SN7jENx9ifC88lkHABEnzgsx9FoQ6hsppKvrU6Vfiy1Kpz/zvt4u1aXRfHj3txQ/UaDdkAK4Uoec=

Solving the problem

No response

Anything else

No response

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[eladkal]

Probably just missing entry in the redirect.txt

[potiuk]

I think it is important to know "where you got the link from" - because like it is wrong there. So the question is how you navigated there @jroachgolf84 ?

[jroachgolf84]

I am navigating here in the following way.

1. Search for "airflow empty operator" in a browser.
2. Navigate to this result: https://airflow.apache.org/docs/apache-airflow/2.6.0/_api/airflow/operators/empty/index.html
3. Try to select Stable (3.0.2) in the upper left.

[arvindp25]

It work till here https://airflow.apache.org/docs/apache-airflow/2.10.4/_api/airflow/operators/empty/index.html
after that error out.

[jroachgolf84]

Bumping this back up - what is the best way to go about remedy'ing this? I'm not sure how redirects.txt is used...

[potiuk]

Bumping this back up - what is the best way to go about remedy'ing this? I'm not sure how redirects.txt is used...

You need to create redirect in redirect.tx from the old location to the new (look at some of the redireections there already) - then next time when documentation is built this thing will happen:

Assume you used to have test/old page and you add redirection to test/new page.

You add this line

test/old -> test/new 

(Can't remember the exact way but follow what's there)

Then when documentation is build, two things are happening:

a) in the NEW version of page (say Airflow 3.0.3) there is the "test/old.html" file generate that performs immediate reload to "test/new.html"

b) in all the PAST versions of the page (Airflow 1.10 -> 3.0.2) the "test/new.html" file is generated that performs immediate reloate to "test/old.html"

This way if you use "stable/test/old" link -> because of a) you will be redirected to "stable/test/new"
But when you are on the "test/new" page and change version "say 2.7.0" the "2.7.0/test/new" page will redirect you to "2.7.0/test/old" - because this is where the old version of the page was.

I hope this clarifies and someone will fix it :)

[potiuk]

Example:

howto/operator/bash.rst ../../apache-airflow-providers-standard/stable/operators/bash.rst
howto/operator/datetime.rst ../../apache-airflow-providers-standard/stable/operators/datetime.rst
howto/operator/external_task_sensor.rst ../../apache-airflow-providers-standard/stable/sensors/external_task_sensor.rst
howto/operator/file.rst ../../apache-airflow-providers-standard/stable/sensors/file.rst
howto/operator/python.rst ../../apache-airflow-providers-standard/stable/operators/python.rst
howto/operator/time.rst ../../apache-airflow-providers-standard/stable/sensors/datetime.rst
howto/operator/weekday.rst ../../apache-airflow-providers-standard/stable/operators/datetime.rst#branchdayofweekoperator

• old = howto/operator/bash.rst
• new = ../../apache-airflow-providers-standard/stable/operators/bash.rst

[suman-himanshu]

I would like to contribute to this issue.