Thanks for the information. Seems the issue is the root cause of the problem. For this specific use case with view, there would be no concern on potential UPSERT SELECT infinite loop since there would be no update.
Not sure on the current status of the issue. Seems there is a patch, but the last integration effort failed according to the auto-generated comments. The target version is set to 4.11, is this still the plan to get it into the next release? (The current latest stable release is 4.10). Thanks again. -- View this message in context: http://apache-phoenix-user-list.1124778.n5.nabble.com/View-timestamp-on-existing-table-potential-defect-tp3475p3489.html Sent from the Apache Phoenix User List mailing list archive at Nabble.com.
