Is your feature request related to a problem?
Currently, we implement alias type by viewing it as a physical column while replacing its resolving path with its referred original path when pushdown or retrieving value.

However, our developers may forget to do path replacement when do push down for the new added feature, if he is not familiar with the current process.

Another proposal to refactor this is removing alias type field in our table schema while putting a project before the original scan to add these alias type fields back. These new addd alias fields are added as the alias(SQL concept) to their referred original fields. Then in scan level, we don't need to handle the path replacement logic.

What solution would you like?
A clear and concise description of what you want to happen.

What alternatives have you considered?
A clear and concise description of any alternative solutions or features you've considered.

Do you have any additional context?
Add any other context or screenshots about the feature request here.