jrgemignani commented on issue #343: URL: https://github.com/apache/age/issues/343#issuecomment-1343064068
@TropicalPenguin @parvit I would like to note that this issue is **currently** being worked on (looked into), by other PMCs and committers, interns in this particular case. Please give them the opportunity to work on it. Especially, since this is a case of where functionality is missing, potentially due to an oversight, and that needs to be addressed. I do appreciate you bringing this issue to our attention! @TropicalPenguin Please hold back on submitting **bounties** for features that aren't implemented yet, or appear to be missed or overlooked. This is an area that PMCs and committers need to address and rectify, using the proper channels and proper procedures - many that you are not a party to. There are a lot of internal discussions, design decisions, and roadmaps that go into a feature - they take time. Plus, we don't want to have a duplication of work and the messiness that may cause. We don't want the **bounties** to start causing issues or too much noise so, let's try to find a happy medium. Do feel free to ask if something falls into this category. Additionally, as a side note, SET, along with the other update commands, are extremely tricky to get functioning correctly due to subtle interactions and requirements. Think, transaction and command ids, begin/commit blocks, chained commands, etc. They are not trivial and there are design considerations and tradeoffs that we need to discuss and make. john -- 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]
