[jira] [Updated] (SOLR-10933) LetStream variables are not evaluated in proper order
[ https://issues.apache.org/jira/browse/SOLR-10933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cassandra Targett updated SOLR-10933: - Component/s: streaming expressions > LetStream variables are not evaluated in proper order > - > > Key: SOLR-10933 > URL: https://issues.apache.org/jira/browse/SOLR-10933 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Components: streaming expressions >Reporter: Joel Bernstein >Assignee: Joel Bernstein > Fix For: 7.0, 6.7 > > Attachments: SOLR-10933.patch > > > The LetStream is currently using a HashMap to hold its variable mappings. > This is problematic because the ordering of the variables will be lost as > they are evaluated. The test cases pass currently because single letter > variables in ascending order are used which by luck caused the variables to > be evaluated in order. > There is a very simple fix for this which is to use a LinkedHashMap to hold > the variables to ensure they are evaluated in the order that they are > received. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-10933) LetStream variables are not evaluated in proper order
[ https://issues.apache.org/jira/browse/SOLR-10933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Bernstein updated SOLR-10933: -- Fix Version/s: 6.7 > LetStream variables are not evaluated in proper order > - > > Key: SOLR-10933 > URL: https://issues.apache.org/jira/browse/SOLR-10933 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) >Reporter: Joel Bernstein > Fix For: master (7.0), 6.7 > > Attachments: SOLR-10933.patch > > > The LetStream is currently using a HashMap to hold its variable mappings. > This is problematic because the ordering of the variables will be lost as > they are evaluated. The test cases pass currently because single letter > variables in ascending order are used which by luck caused the variables to > be evaluated in order. > There is a very simple fix for this which is to use a LinkedHashMap to hold > the variables to ensure they are evaluated in the order that they are > received. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-10933) LetStream variables are not evaluated in proper order
[ https://issues.apache.org/jira/browse/SOLR-10933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Bernstein updated SOLR-10933: -- Fix Version/s: master (7.0) > LetStream variables are not evaluated in proper order > - > > Key: SOLR-10933 > URL: https://issues.apache.org/jira/browse/SOLR-10933 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) >Reporter: Joel Bernstein > Fix For: master (7.0) > > Attachments: SOLR-10933.patch > > > The LetStream is currently using a HashMap to hold its variable mappings. > This is problematic because the ordering of the variables will be lost as > they are evaluated. The test cases pass currently because single letter > variables in ascending order are used which by luck caused the variables to > be evaluated in order. > There is a very simple fix for this which is to use a LinkedHashMap to hold > the variables to ensure they are evaluated in the order that they are > received. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-10933) LetStream variables are not evaluated in proper order
[ https://issues.apache.org/jira/browse/SOLR-10933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Bernstein updated SOLR-10933: -- Attachment: SOLR-10933.patch Simple fix and change to a test case to verify the variables are being evaluated in order. > LetStream variables are not evaluated in proper order > - > > Key: SOLR-10933 > URL: https://issues.apache.org/jira/browse/SOLR-10933 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) >Reporter: Joel Bernstein > Attachments: SOLR-10933.patch > > > The LetStream is currently using a HashMap to hold its variable mappings. > This is problematic because the ordering of the variables will be lost as > they are evaluated. The test cases pass currently because single letter > variables in ascending order are used which by luck caused the variables to > be evaluated in order. > There is a very simple fix for this which is to use a LinkedHashMap to hold > the variables to ensure they are evaluated in the order that they are > received. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-10933) LetStream variables are not evaluated in proper order
[ https://issues.apache.org/jira/browse/SOLR-10933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Bernstein updated SOLR-10933: -- Description: The LetStream is currently using a HashMap to hold its variable mappings. This is problematic because the ordering of the variables will be lost as they are evaluated. The test cases pass currently because single letter variables in ascending order are used which by luck caused the variables to be evaluated in order. There is a very simple fix for this which is to use a LinkedHashMap to hold the variables to ensure they are evaluated in the order that they are received. was: The LetStream is currently using a HashMap to hold its variable mappings. This is problematic because the ordering of the variables will lost as they are evaluated. The test cases pass currently because single letter variables in ascending order are used which by luck caused the variables to be evaluated in order. There is a very simple fix for this which is to use a LinkedHashMap to hold the variables to ensure they are evaluated in the order that they are received. > LetStream variables are not evaluated in proper order > - > > Key: SOLR-10933 > URL: https://issues.apache.org/jira/browse/SOLR-10933 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) >Reporter: Joel Bernstein > > The LetStream is currently using a HashMap to hold its variable mappings. > This is problematic because the ordering of the variables will be lost as > they are evaluated. The test cases pass currently because single letter > variables in ascending order are used which by luck caused the variables to > be evaluated in order. > There is a very simple fix for this which is to use a LinkedHashMap to hold > the variables to ensure they are evaluated in the order that they are > received. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-10933) LetStream variables are not evaluated in proper order
[ https://issues.apache.org/jira/browse/SOLR-10933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Bernstein updated SOLR-10933: -- Description: The LetStream is currently using a HashMap to hold its variable mappings. This is problematic because the ordering of the variables will lost as they are evaluated. The test cases pass currently because single letter variables in ascending order are used which by luck caused the variables to be evaluated in order. There is a very simple fix for this which is to use a LinkedHashMap to hold the variables to ensure they are evaluated in the order that they are received. was: The LetStream is currently using a HashMap to hold it variable mappings. This is problematic because the ordering of the variables will lost as they are evaluated. The test cases pass currently because single letter variables in ascending order are used which by luck caused the variables to be evaluated in order. There is a very simple fix for this which is to use a LinkedHashMap to hold the variables to ensure they are evaluated in the order that they are received. > LetStream variables are not evaluated in proper order > - > > Key: SOLR-10933 > URL: https://issues.apache.org/jira/browse/SOLR-10933 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) >Reporter: Joel Bernstein > > The LetStream is currently using a HashMap to hold its variable mappings. > This is problematic because the ordering of the variables will lost as they > are evaluated. The test cases pass currently because single letter variables > in ascending order are used which by luck caused the variables to be > evaluated in order. > There is a very simple fix for this which is to use a LinkedHashMap to hold > the variables to ensure they are evaluated in the order that they are > received. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
