muyangye commented on issue #2181: URL: https://github.com/apache/streampipes/issues/2181#issuecomment-1850910169
> I like the proposal of #2300. How do want to handle `internalFilename` and `originalFilename` in this case? I agree that #2300 is a good compromise between this feature and stability for the end user. In the middle term, I'd like to remove the distinction code-wise as well. #2300 is just a temporary PR so that everyone can see my current approach, for merging the `internalFilename` and `originalFilename`, I plan to achieve this by the migration too. I am not sure what will happen if I modify the `FileMetadata` class structure and then commit the update to CouchDB. I will check it out later. I propose #2300 first because 1. That at least allows users to see no duplicate `originalFilename` and the REST and UI change are necessary even after merging `internalFilename` and `originalFilename`. 2. I will be traveling around in the upcoming 3 weeks. So I might not be able to work until early January. I don't think I can finish the merging before my travel so I submitted #2300 as a temporary solution. I will finish the entire migration later 🥇 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
