[jira] [Commented] (DERBY-4115) Provide a way to drop statistics information
[ https://issues.apache.org/jira/browse/DERBY-4115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280195#comment-13280195 ] Kristian Waagan commented on DERBY-4115: suites.All completed with patch 7a. Committed to trunk with revision 1341059. > Provide a way to drop statistics information > > > Key: DERBY-4115 > URL: https://issues.apache.org/jira/browse/DERBY-4115 > Project: Derby > Issue Type: Improvement > Components: SQL >Affects Versions: 10.6.1.0 >Reporter: Kathey Marsden >Assignee: Mamta A. Satoor > Labels: derby_backport_reject_10_8 > Fix For: 10.9.0.0 > > Attachments: DERBY4115_patch1_diff.txt, DERBY4115_patch2_diff.txt, > DERBY4115_patch3_diff.txt, DERBY4115_patch4_diff.txt, > DERBY4115_patch5_diff.txt, DERBY4115_patch6_diff.txt, > derby-4115-7a-move_test.diff > > > Now that DERBY-269 has been resolved, users can update statistics, but once > they do, they are committed to using and maintaining the statistics, even if > it doesn't improve performance or they have difficulty maintaining the > statistics on a regular basis. It would be good to have a way to drop > statistics information so that users could revert to the prior behavior if > needed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DERBY-4115) Provide a way to drop statistics information
[ https://issues.apache.org/jira/browse/DERBY-4115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13271057#comment-13271057 ] Mamta A. Satoor commented on DERBY-4115: Created following jira for exception thrown when empty string is passed for index name to update/drop statistics procedures DERBY-5750 Sending an empty string as table name to compress table procedure or empty string as index name to update statistics procedure makes the parser throw an exception. > Provide a way to drop statistics information > > > Key: DERBY-4115 > URL: https://issues.apache.org/jira/browse/DERBY-4115 > Project: Derby > Issue Type: Improvement > Components: SQL >Affects Versions: 10.6.1.0 >Reporter: Kathey Marsden >Assignee: Mamta A. Satoor > Attachments: DERBY4115_patch1_diff.txt, DERBY4115_patch2_diff.txt, > DERBY4115_patch3_diff.txt, DERBY4115_patch4_diff.txt, > DERBY4115_patch5_diff.txt > > > Now that DERBY-269 has been resolved, users can update statistics, but once > they do, they are committed to using and maintaining the statistics, even if > it doesn't improve performance or they have difficulty maintaining the > statistics on a regular basis. It would be good to have a way to drop > statistics information so that users could revert to the prior behavior if > needed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DERBY-4115) Provide a way to drop statistics information
[ https://issues.apache.org/jira/browse/DERBY-4115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13271039#comment-13271039 ] Mamta A. Satoor commented on DERBY-4115: Kristian, as for your following comment d) SystemProcedures.SYSCS_DROP_STATISTICS: o Also, I don't understand the comment about indexname being the empty string. Is that allowed? The parser falls over if I try to specify it as an argument to the SQL call. You are right, that giving an empty string makes the parse give following exception. I tried using empty string with compress table/update statistics procedure and saw the same behavior. I will go ahead and file a jira for that issue in general. ij> call syscs_util.SYSCS_DROP_STATISTICS( 'APP', 'T1', '' ); ERROR 38000: The exception 'java.sql.SQLException: Syntax error: Encountered "\"" at line 1, column 40.' was thrown while evaluating an expression. java.sql.SQLException: The exception 'java.sql.SQLException: Syntax error: Encountered "\"" at line 1, column 40.' was thrown while evaluating an expression. at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(SQLExceptionFactory40.java:98) at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Util.java:142) at org.apache.derby.impl.jdbc.Util.seeNextException(Util.java:278) at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(TransactionResourceImpl.java:431) at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(TransactionResourceImpl.java:353) at org.apache.derby.impl.jdbc.EmbedConnection.handleException(EmbedConnection.java:2360) at org.apache.derby.impl.jdbc.ConnectionChild.handleException(ConnectionChild.java:82) at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(EmbedStatement.java:1334) at org.apache.derby.impl.jdbc.EmbedStatement.execute(EmbedStatement.java:630) at org.apache.derby.impl.jdbc.EmbedStatement.execute(EmbedStatement.java:559) at org.apache.derby.impl.tools.ij.ij.executeImmediate(ij.java:367) at org.apache.derby.impl.tools.ij.utilMain.doCatch(utilMain.java:527) at org.apache.derby.impl.tools.ij.utilMain.runScriptGuts(utilMain.java:369) at org.apache.derby.impl.tools.ij.utilMain.go(utilMain.java:245) at org.apache.derby.impl.tools.ij.Main.go(Main.java:229) at org.apache.derby.impl.tools.ij.Main.mainCore(Main.java:184) at org.apache.derby.impl.tools.ij.Main.main(Main.java:75) at org.apache.derby.tools.ij.main(ij.java:59) Caused by: java.sql.SQLException: The exception 'java.sql.SQLException: Syntax error: Encountered "\"" at line 1, column 40.' was thrown while evaluating an expression. at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(SQLExceptionFactory.java:42) at org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(SQLExceptionFactory40.java:122) at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(SQLExceptionFactory40.java:71) ... 17 more Caused by: java.sql.SQLException: Syntax error: Encountered "\"" at line 1, column 40. at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(SQLExceptionFactory.java:42) at org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(SQLExceptionFactory40.java:122) at org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(SQLExceptionFactory40.java:71) at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Util.java:256) at org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(TransactionResourceImpl.java:424) at org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(TransactionResourceImpl.java:353) at org.apache.derby.impl.jdbc.EmbedConnection.handleException(EmbedConnection.java:2360) at org.apache.derby.impl.jdbc.ConnectionChild.handleException(ConnectionChild.java:82) at org.apache.derby.impl.jdbc.EmbedPreparedStatement.(EmbedPreparedStatement.java:153) at org.apache.derby.jdbc.Driver40.newEmbedPreparedStatement(Driver40.java:107) at org.apache.derby.impl.jdbc.EmbedConnection.prepareStatement(EmbedConnection.java:1685) at org.apache.derby.impl.jdbc.EmbedConnection.prepareStatement(EmbedConnection.java:1513) at org.apache.derby.catalog.SystemProcedures.SYSCS_DROP_STATISTICS(SystemProcedures.java:792) at org.apache.derby.exe.acace4c0a3x0137x2f19xcc22x0013e5701.g0(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.M
[jira] [Commented] (DERBY-4115) Provide a way to drop statistics information
[ https://issues.apache.org/jira/browse/DERBY-4115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13270864#comment-13270864 ] Mamta A. Satoor commented on DERBY-4115: Kristian, thanks for taking the time to review the patch. Here are my answers. a) Inconsistent use of tabs and spaces for indentation. I will fix this. Not sure why Eclipse is not consistent in using one vs the others. b) Would it be okay to use (indexNameForStatistics == null) instead of dropStatisticsAll to reduce the state of the class? The relationship could be documented with dropStatistics. I wondered about this myself when I copied the model for update statistics for drop statistics. My gut feeling is that this was done in order to avoid the conflict with pre-existing 4 parameter init() method for compress table and hence we may have decided to add a new init method with 5 parameters but I am not 100% sure about this theory. I am planning on uploading a patch soon which will update upgrade tests and more regular tests for drop statistics. If there are no comments on that patch, I would like to go ahead and commit that patch. We can address the redundancy of extra parameter dropStatisticsAll/updateStatisticsAll in a future patch. c) Typo in sqlgrammar.jj "By the type" -> "By the time" I will fix this. d) SystemProcedures.SYSCS_DROP_STATISTICS: o typo in @param indexname. Also, I don't understand the comment about indexname being the empty string. Is that allowed? The parser falls over if I try to specify it as an argument to the SQL call. o incorrect @exception (or @throws) in Javadoc o debug println I will fix this. e) What's the reason for the change in Changes10_2? The test after hard upgrades seem to check how many system procedures have public access. Since the drop statistics procedure has public access(similar to update statistics), we need to include that in the expected resultset list. > Provide a way to drop statistics information > > > Key: DERBY-4115 > URL: https://issues.apache.org/jira/browse/DERBY-4115 > Project: Derby > Issue Type: Improvement > Components: SQL >Affects Versions: 10.6.1.0 >Reporter: Kathey Marsden >Assignee: Mamta A. Satoor > Attachments: DERBY4115_patch1_diff.txt, DERBY4115_patch2_diff.txt, > DERBY4115_patch3_diff.txt, DERBY4115_patch4_diff.txt, > DERBY4115_patch5_diff.txt > > > Now that DERBY-269 has been resolved, users can update statistics, but once > they do, they are committed to using and maintaining the statistics, even if > it doesn't improve performance or they have difficulty maintaining the > statistics on a regular basis. It would be good to have a way to drop > statistics information so that users could revert to the prior behavior if > needed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DERBY-4115) Provide a way to drop statistics information
[ https://issues.apache.org/jira/browse/DERBY-4115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13269538#comment-13269538 ] Kristian Waagan commented on DERBY-4115: Hi Mamta, I had a look at patch 5. The tests ran sucessfully, and my simple manual invokations behaved like they should. Here are some comments, suggestions, and questions about the patch: a) Inconsistent use of tabs and spaces for indentation. b) Would it be okay to use (indexNameForStatistics == null) instead of dropStatisticsAll to reduce the state of the class? The relationship could be documented with dropStatistics. c) Typo in sqlgrammar.jj "By the type" -> "By the time" d) SystemProcedures.SYSCS_DROP_STATISTICS: o typo in @param indexname. Also, I don't understand the comment about indexname being the empty string. Is that allowed? The parser falls over if I try to specify it as an argument to the SQL call. o incorrect @exception (or @throws) in Javadoc o debug println e) What's the reason for the change in Changes10_2? Thanks, > Provide a way to drop statistics information > > > Key: DERBY-4115 > URL: https://issues.apache.org/jira/browse/DERBY-4115 > Project: Derby > Issue Type: Improvement > Components: SQL >Affects Versions: 10.6.1.0 >Reporter: Kathey Marsden >Assignee: Mamta A. Satoor > Attachments: DERBY4115_patch1_diff.txt, DERBY4115_patch2_diff.txt, > DERBY4115_patch3_diff.txt, DERBY4115_patch4_diff.txt, > DERBY4115_patch5_diff.txt > > > Now that DERBY-269 has been resolved, users can update statistics, but once > they do, they are committed to using and maintaining the statistics, even if > it doesn't improve performance or they have difficulty maintaining the > statistics on a regular basis. It would be good to have a way to drop > statistics information so that users could revert to the prior behavior if > needed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DERBY-4115) Provide a way to drop statistics information
[ https://issues.apache.org/jira/browse/DERBY-4115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13263300#comment-13263300 ] Mamta A. Satoor commented on DERBY-4115: Hi Bryan, thanks for looking at the patch. The syntax indeed is "ALL DROP STATISTICS". It pretty much mirrors what we have implemented for updated statistics which has the internal syntax of "ALL UPDATE STATISTICS". I am not sure why we chose it to be that way. May be it was easier to implement it that way in the parser and since this is internal only syntax, may be we decided to go ahead with "ALL UPDATE STATISTICS" rather than "UPDATE ALL STATISTICS". > Provide a way to drop statistics information > > > Key: DERBY-4115 > URL: https://issues.apache.org/jira/browse/DERBY-4115 > Project: Derby > Issue Type: Improvement > Components: SQL >Affects Versions: 10.6.1.0 >Reporter: Kathey Marsden >Assignee: Mamta A. Satoor > Attachments: DERBY4115_patch1_diff.txt, DERBY4115_patch2_diff.txt, > DERBY4115_patch3_diff.txt, DERBY4115_patch4_diff.txt > > > Now that DERBY-269 has been resolved, users can update statistics, but once > they do, they are committed to using and maintaining the statistics, even if > it doesn't improve performance or they have difficulty maintaining the > statistics on a regular basis. It would be good to have a way to drop > statistics information so that users could revert to the prior behavior if > needed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DERBY-4115) Provide a way to drop statistics information
[ https://issues.apache.org/jira/browse/DERBY-4115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13263284#comment-13263284 ] Bryan Pendleton commented on DERBY-4115: Is this syntax just an example? Or is this the intended syntax? I'm trying to figure out what the word "ALL" means in "ALL DROP STATISTICS", and whether it should be "DROP ALL STATISTICS" instead. > Provide a way to drop statistics information > > > Key: DERBY-4115 > URL: https://issues.apache.org/jira/browse/DERBY-4115 > Project: Derby > Issue Type: Improvement > Components: SQL >Affects Versions: 10.6.1.0 >Reporter: Kathey Marsden >Assignee: Mamta A. Satoor > Attachments: DERBY4115_patch1_diff.txt, DERBY4115_patch2_diff.txt, > DERBY4115_patch3_diff.txt, DERBY4115_patch4_diff.txt > > > Now that DERBY-269 has been resolved, users can update statistics, but once > they do, they are committed to using and maintaining the statistics, even if > it doesn't improve performance or they have difficulty maintaining the > statistics on a regular basis. It would be good to have a way to drop > statistics information so that users could revert to the prior behavior if > needed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DERBY-4115) Provide a way to drop statistics information
[ https://issues.apache.org/jira/browse/DERBY-4115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13261884#comment-13261884 ] Mamta A. Satoor commented on DERBY-4115: As the next step, I am looking at actually implementing the routine now that the ground work is done. I think the implementation should be similar to update statistics, ie allow the code to go through ALTER TABLE where permission/privilege checking, table/schema/index name validations happen automatically and we can implement the routine through ALTER TABLE. This will require changing ALTER TABLE syntax(same as we did for update statistics) but it will be an internal syntax and won't be available to an end user directly. > Provide a way to drop statistics information > > > Key: DERBY-4115 > URL: https://issues.apache.org/jira/browse/DERBY-4115 > Project: Derby > Issue Type: Improvement > Components: SQL >Affects Versions: 10.6.1.0 >Reporter: Kathey Marsden >Assignee: Mamta A. Satoor > Attachments: DERBY4115_patch1_diff.txt, DERBY4115_patch2_diff.txt, > DERBY4115_patch3_diff.txt > > > Now that DERBY-269 has been resolved, users can update statistics, but once > they do, they are committed to using and maintaining the statistics, even if > it doesn't improve performance or they have difficulty maintaining the > statistics on a regular basis. It would be good to have a way to drop > statistics information so that users could revert to the prior behavior if > needed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DERBY-4115) Provide a way to drop statistics information
[ https://issues.apache.org/jira/browse/DERBY-4115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260783#comment-13260783 ] Mike Matrigali commented on DERBY-4115: --- I am good with the name of the procedure, and with respect to roles and permissions I think it should just function the same way as update statistics routine does. > Provide a way to drop statistics information > > > Key: DERBY-4115 > URL: https://issues.apache.org/jira/browse/DERBY-4115 > Project: Derby > Issue Type: Improvement > Components: SQL >Affects Versions: 10.6.1.0 >Reporter: Kathey Marsden >Assignee: Mamta A. Satoor > Attachments: DERBY4115_patch1_diff.txt > > > Now that DERBY-269 has been resolved, users can update statistics, but once > they do, they are committed to using and maintaining the statistics, even if > it doesn't improve performance or they have difficulty maintaining the > statistics on a regular basis. It would be good to have a way to drop > statistics information so that users could revert to the prior behavior if > needed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DERBY-4115) Provide a way to drop statistics information
[ https://issues.apache.org/jira/browse/DERBY-4115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260712#comment-13260712 ] Mike Matrigali commented on DERBY-4115: --- >t's been a while since I looked into upgrade and stored procedures. Does the >restriction above come from the fact that we can't support >the alternative >behavior? That would be to allow the procedure to be called on a soft upgraded >database to remove orphaned statistics, >and then continue using the older >version afterwards. This way the problem can be fixed without moving off the >current Derby version. >Even if the above is technically possible, I'm fine with forbidding it if it >conflicts with our current policy. I was just a bit curious :) I think it "might" be possible, but that we should not do it for soft upgrade. The idea with soft upgrade is that a user should be able to run 10.9 software in soft upgrade mode and then go back to running 10.1 software if it is a 10.1 database. If their application has calls to the new drop statistics routine it is very likely not to work when run in 10.1 software and we don't want to be supporting that. This specific routine might work for some subset of situation, but the policy to disable new syntax features in soft upgrade seems clean and leads to easily understood behavior, rather than allow some and not others. > Provide a way to drop statistics information > > > Key: DERBY-4115 > URL: https://issues.apache.org/jira/browse/DERBY-4115 > Project: Derby > Issue Type: Improvement > Components: SQL >Affects Versions: 10.6.1.0 >Reporter: Kathey Marsden >Assignee: Mamta A. Satoor > Attachments: DERBY4115_patch1_diff.txt > > > Now that DERBY-269 has been resolved, users can update statistics, but once > they do, they are committed to using and maintaining the statistics, even if > it doesn't improve performance or they have difficulty maintaining the > statistics on a regular basis. It would be good to have a way to drop > statistics information so that users could revert to the prior behavior if > needed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DERBY-4115) Provide a way to drop statistics information
[ https://issues.apache.org/jira/browse/DERBY-4115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260706#comment-13260706 ] Mamta A. Satoor commented on DERBY-4115: I forgot to mention in my earlier patch that I have given the new routine(SYSCS_DROP_STATISTICS) public access (same as existing update statistics procedure). This happens in DataDictionaryImpl, where SYSCS_DROP_STATISTICS is added to the list of public access procedures in sysUtilProceduresWithPublicAccess. Just wanted to bring this up since it is not very obvious. Thanks Also, please let me know if we should use a different name for this procedure. I am using SYSCS_DROP_STATISTICS in the attached patch. > Provide a way to drop statistics information > > > Key: DERBY-4115 > URL: https://issues.apache.org/jira/browse/DERBY-4115 > Project: Derby > Issue Type: Improvement > Components: SQL >Affects Versions: 10.6.1.0 >Reporter: Kathey Marsden >Assignee: Mamta A. Satoor > Attachments: DERBY4115_patch1_diff.txt > > > Now that DERBY-269 has been resolved, users can update statistics, but once > they do, they are committed to using and maintaining the statistics, even if > it doesn't improve performance or they have difficulty maintaining the > statistics on a regular basis. It would be good to have a way to drop > statistics information so that users could revert to the prior behavior if > needed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DERBY-4115) Provide a way to drop statistics information
[ https://issues.apache.org/jira/browse/DERBY-4115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260399#comment-13260399 ] Kristian Waagan commented on DERBY-4115: > Next, I plan to write upgrade test to make sure that this method will not be > available on pre-10.9 dbs, soft=upgraded dbs. It should only be available on > hard upgraded dbs. It's been a while since I looked into upgrade and stored procedures. Does the restriction above come from the fact that we can't support the alternative behavior? That would be to allow the procedure to be called on a soft upgraded database to remove orphaned statistics, and then continue using the older version afterwards. This way the problem can be fixed without moving off the current Derby version. Even if the above is technically possible, I'm fine with forbidding it if it conflicts with our current policy. I was just a bit curious :) > Provide a way to drop statistics information > > > Key: DERBY-4115 > URL: https://issues.apache.org/jira/browse/DERBY-4115 > Project: Derby > Issue Type: Improvement > Components: SQL >Affects Versions: 10.6.1.0 >Reporter: Kathey Marsden >Assignee: Mamta A. Satoor > Attachments: DERBY4115_patch1_diff.txt > > > Now that DERBY-269 has been resolved, users can update statistics, but once > they do, they are committed to using and maintaining the statistics, even if > it doesn't improve performance or they have difficulty maintaining the > statistics on a regular basis. It would be good to have a way to drop > statistics information so that users could revert to the prior behavior if > needed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DERBY-4115) Provide a way to drop statistics information
[ https://issues.apache.org/jira/browse/DERBY-4115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260056#comment-13260056 ] Mike Matrigali commented on DERBY-4115: --- I suggest an incremental approach, but add enough arguments for future expansion. I would think a good first step would be a call that dropped all the statistics for a single table. So include schema, table and indexname arguments, but for first step only support null for indexname which would mean drop all stats for a table. Next step might be to support dropping just those stats on a particular index. > Provide a way to drop statistics information > > > Key: DERBY-4115 > URL: https://issues.apache.org/jira/browse/DERBY-4115 > Project: Derby > Issue Type: Improvement > Components: SQL >Affects Versions: 10.6.1.0 >Reporter: Kathey Marsden >Assignee: Mamta A. Satoor > > Now that DERBY-269 has been resolved, users can update statistics, but once > they do, they are committed to using and maintaining the statistics, even if > it doesn't improve performance or they have difficulty maintaining the > statistics on a regular basis. It would be good to have a way to drop > statistics information so that users could revert to the prior behavior if > needed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DERBY-4115) Provide a way to drop statistics information
[ https://issues.apache.org/jira/browse/DERBY-4115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13259826#comment-13259826 ] Mamta A. Satoor commented on DERBY-4115: Are we talking about dropping statistics for a specific table or all the tables in a given schema? I think either could be implemented but wanted to double check the scope of the procedure. > Provide a way to drop statistics information > > > Key: DERBY-4115 > URL: https://issues.apache.org/jira/browse/DERBY-4115 > Project: Derby > Issue Type: Improvement > Components: SQL >Affects Versions: 10.6.1.0 >Reporter: Kathey Marsden >Assignee: Mamta A. Satoor > > Now that DERBY-269 has been resolved, users can update statistics, but once > they do, they are committed to using and maintaining the statistics, even if > it doesn't improve performance or they have difficulty maintaining the > statistics on a regular basis. It would be good to have a way to drop > statistics information so that users could revert to the prior behavior if > needed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DERBY-4115) Provide a way to drop statistics information
[ https://issues.apache.org/jira/browse/DERBY-4115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13244305#comment-13244305 ] Mike Matrigali commented on DERBY-4115: --- Of course can't say without seeing an implementation, but I can't think of potential issues for not implementing this. And give DERBY-5681 it seems even more useful. One problem is I don't think we can backport this feature, as adding a new system procedure would create compatibility/upgrade issues. So would not help 10.8 users but would help in the future for 10.9 and above. And it would be great if the implementation handled the unexpected rows caused by DERBY-5681, since even after this bug is fixed we may always in the future still see these rows as people upgrade old dbs to new derby versions. > Provide a way to drop statistics information > > > Key: DERBY-4115 > URL: https://issues.apache.org/jira/browse/DERBY-4115 > Project: Derby > Issue Type: Improvement > Components: SQL >Affects Versions: 10.6.1.0 >Reporter: Kathey Marsden > > Now that DERBY-269 has been resolved, users can update statistics, but once > they do, they are committed to using and maintaining the statistics, even if > it doesn't improve performance or they have difficulty maintaining the > statistics on a regular basis. It would be good to have a way to drop > statistics information so that users could revert to the prior behavior if > needed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DERBY-4115) Provide a way to drop statistics information
[ https://issues.apache.org/jira/browse/DERBY-4115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13244029#comment-13244029 ] Kristian Waagan commented on DERBY-4115: This seems like a simple system procedure to implement, and could be useful now that automatic updates of index cardinality statistics is enabled by default. We just saw a user report where the statistics were messed up due to a bug in Derby, and this caused the istat daemon to go crazy. A bug in the daemon itself would also be easier to work around if it is possible to discard existing statistics after the daemon has been disabled. Has this feature never been implemented due to lack of demand, or are there potential issues that haven't been noted in this JIRA? > Provide a way to drop statistics information > > > Key: DERBY-4115 > URL: https://issues.apache.org/jira/browse/DERBY-4115 > Project: Derby > Issue Type: Improvement > Components: SQL >Affects Versions: 10.6.1.0 >Reporter: Kathey Marsden > > Now that DERBY-269 has been resolved, users can update statistics, but once > they do, they are committed to using and maintaining the statistics, even if > it doesn't improve performance or they have difficulty maintaining the > statistics on a regular basis. It would be good to have a way to drop > statistics information so that users could revert to the prior behavior if > needed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
