tonysun83 commented on issue #962: Mango: generate a warning instead of an error when an user-specified index cannot be used URL: https://github.com/apache/couchdb/pull/962#issuecomment-344127263 Wanted to clarify a bit: For scenario 1): I agree that fixing the difference between text and json indexes is outside the scope of the PR, but I was thinking about the specific backwards-compatibility situation where a user specifies ```use_index``` for a json index, and it fails, and the fallback is a text index. Would we rather have them possibly get different results and complain later down the road versus failing them right away with an error? For scenario 2): Similarly to scenario 1), the issue is whether or not the fallback leads to inadvertent changes for the user. In this case, he is modifying his indexes based on perceived notion of what is being used. The performance degradation for _all_docs is noticed and he complains about the issue. We notify him saying that an index was deleted, but he says the index wasn't being used. Now he says ok he wants to rebuild an index...and that may take a long time and negatively affect his cluster. I wonder if it's better to explicitly send back index names as part an failure error message. But could that be a security risk?
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
