[jira] [Commented] (IGNITE-8293) BinaryUtils#isCustomJavaSerialization fails when only readObject is declared in a class
[ https://issues.apache.org/jira/browse/IGNITE-8293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16460624#comment-16460624 ] ASF GitHub Bot commented on IGNITE-8293: GitHub user Celos opened a pull request: https://github.com/apache/ignite/pull/3941 IGNITE-8293 BinaryUtils#isCustomJavaSerialization fails when only rea… …dObject is declared in a class You can merge this pull request into a Git repository by running: $ git pull https://github.com/Celos/ignite ignite-8293 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/3941.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #3941 commit d501f1c450f4c27bfd7f7efe383453318945cee5 Author: Mihkel Jõhvik Date: 2018-05-02T07:30:59Z IGNITE-8293 BinaryUtils#isCustomJavaSerialization fails when only readObject is declared in a class > BinaryUtils#isCustomJavaSerialization fails when only readObject is declared > in a class > --- > > Key: IGNITE-8293 > URL: https://issues.apache.org/jira/browse/IGNITE-8293 > Project: Ignite > Issue Type: Bug > Components: binary >Affects Versions: 2.4 >Reporter: MihkelJ >Assignee: MihkelJ >Priority: Minor > Fix For: 2.6 > > Attachments: IGNITE-8293.patch > > > Consider this class: > > {code:java} > public class Test implements Serializable { > private transient AtomicBoolean dirty = new AtomicBoolean(false); > private void readObject(java.io.ObjectInputStream in) throws IOException, > ClassNotFoundException { > dirty = new AtomicBoolean(false); > } > //methods to check and mark class as dirty > }{code} > {{isCustomJavaSerialization}} will get a {{NoSuchMethodException}} when > trying to grab the {{writeObject}} method and falsely conclude that Test > doesn't use custom serialization. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-6937) SQL TX: Support SELECT FOR UPDATE
[ https://issues.apache.org/jira/browse/IGNITE-6937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Paschenko updated IGNITE-6937: Attachment: Снимок экрана 2018-05-02 в 11.51.03.png > SQL TX: Support SELECT FOR UPDATE > - > > Key: IGNITE-6937 > URL: https://issues.apache.org/jira/browse/IGNITE-6937 > Project: Ignite > Issue Type: Task > Components: cache, sql >Reporter: Vladimir Ozerov >Assignee: Alexander Paschenko >Priority: Major > Labels: iep-3 > Fix For: 2.6 > > Attachments: Снимок экрана 2018-05-02 в 11.51.03.png > > > Normally in SQL world readers do not block writers. This is how our SELECT > operations should work by default. But we need to add a support for {{SELECT > ... FOR UPDATE}} read mode, when reader obtains exclusive lock on read. > In this mode we lock entries as usual, but then send data back to the caller. > First page can be returned directly in our {{LockResponse}}. Next pages > should be requested in separate requests. With this approach {{SELECT ,,, FOR > UPDATE}} will require only single round-trip to both lock and read data in > case of small updates. > Update {{SELECT}} statement syntax once this feature is supported: > https://apacheignite-sql.readme.io/docs/select -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-6937) SQL TX: Support SELECT FOR UPDATE
[ https://issues.apache.org/jira/browse/IGNITE-6937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16460824#comment-16460824 ] Alexander Paschenko commented on IGNITE-6937: - [~vozerov], all fixed. > SQL TX: Support SELECT FOR UPDATE > - > > Key: IGNITE-6937 > URL: https://issues.apache.org/jira/browse/IGNITE-6937 > Project: Ignite > Issue Type: Task > Components: cache, sql >Reporter: Vladimir Ozerov >Assignee: Alexander Paschenko >Priority: Major > Labels: iep-3 > Fix For: 2.6 > > Attachments: Снимок экрана 2018-05-02 в 11.51.03.png > > > Normally in SQL world readers do not block writers. This is how our SELECT > operations should work by default. But we need to add a support for {{SELECT > ... FOR UPDATE}} read mode, when reader obtains exclusive lock on read. > In this mode we lock entries as usual, but then send data back to the caller. > First page can be returned directly in our {{LockResponse}}. Next pages > should be requested in separate requests. With this approach {{SELECT ,,, FOR > UPDATE}} will require only single round-trip to both lock and read data in > case of small updates. > Update {{SELECT}} statement syntax once this feature is supported: > https://apacheignite-sql.readme.io/docs/select -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8293) BinaryUtils#isCustomJavaSerialization fails when only readObject is declared in a class
[ https://issues.apache.org/jira/browse/IGNITE-8293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16460908#comment-16460908 ] MihkelJ commented on IGNITE-8293: - [~agura], can you help me with this? I've created a pull request, but I'm not sure which test suite to run to verify it. The "all" plan failed spectacularly (https://ci.ignite.apache.org/viewLog.html?buildId=1259899&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_RunAll) and I'm having a hard time believing that my minor change caused all that. > BinaryUtils#isCustomJavaSerialization fails when only readObject is declared > in a class > --- > > Key: IGNITE-8293 > URL: https://issues.apache.org/jira/browse/IGNITE-8293 > Project: Ignite > Issue Type: Bug > Components: binary >Affects Versions: 2.4 >Reporter: MihkelJ >Assignee: MihkelJ >Priority: Minor > Fix For: 2.6 > > Attachments: IGNITE-8293.patch > > > Consider this class: > > {code:java} > public class Test implements Serializable { > private transient AtomicBoolean dirty = new AtomicBoolean(false); > private void readObject(java.io.ObjectInputStream in) throws IOException, > ClassNotFoundException { > dirty = new AtomicBoolean(false); > } > //methods to check and mark class as dirty > }{code} > {{isCustomJavaSerialization}} will get a {{NoSuchMethodException}} when > trying to grab the {{writeObject}} method and falsely conclude that Test > doesn't use custom serialization. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-8272) Add documentation for normalization preprocessor (release 2.5)
[ https://issues.apache.org/jira/browse/IGNITE-8272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akmal Chaudhri reassigned IGNITE-8272: -- Assignee: Prachi Garg (was: Akmal Chaudhri) Prachi, I have reviewed and edited the doc page. Please review when you have time. Thank you. > Add documentation for normalization preprocessor (release 2.5) > -- > > Key: IGNITE-8272 > URL: https://issues.apache.org/jira/browse/IGNITE-8272 > Project: Ignite > Issue Type: Improvement > Components: documentation, ml >Affects Versions: 2.5 >Reporter: Anton Dmitriev >Assignee: Prachi Garg >Priority: Major > Fix For: 2.5 > > > In Apache Ignite 2.5 we have added a normalization preprocessor working on > top of partition based dataset and now we need to add documentation for this > feature. > Affected pages: > [Preprocessing|https://apacheignite.readme.io/v2.4/docs/preprocessing-25] > In release 2.5 > [https://apacheignite.readme.io/v2.4/docs/preprocessing-25|https://apacheignite.readme.io/v2.4/docs/preprocessing-25] > page should be added. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-8268) Add documentation for linear regression (release 2.5)
[ https://issues.apache.org/jira/browse/IGNITE-8268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akmal Chaudhri reassigned IGNITE-8268: -- Assignee: Prachi Garg (was: Akmal Chaudhri) Prachi, I have reviewed and edited the doc page. Please review when you have time. Thank you. > Add documentation for linear regression (release 2.5) > - > > Key: IGNITE-8268 > URL: https://issues.apache.org/jira/browse/IGNITE-8268 > Project: Ignite > Issue Type: Improvement > Components: documentation, ml >Affects Versions: 2.5 >Reporter: Anton Dmitriev >Assignee: Prachi Garg >Priority: Major > Fix For: 2.5 > > > In Apache Ignite 2.5 we have added two implementation of linear regression > based on partition based dataset: LSQR and gradient descent and now we need > to add documentation for these features. > Affected pages: > [Linear > Regression|https://apacheignite.readme.io/v2.4/docs/linear-regression-25] > In release 2.5 > [https://apacheignite.readme.io/v2.4/docs/ols-multiple-linear-regression|https://apacheignite.readme.io/v2.4/docs/ols-multiple-linear-regression] > should be changed to > [https://apacheignite.readme.io/docs/linear-regression-25|https://apacheignite.readme.io/docs/linear-regression-25]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-8271) Add documentation for partition based dataset (release 2.5)
[ https://issues.apache.org/jira/browse/IGNITE-8271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akmal Chaudhri reassigned IGNITE-8271: -- Assignee: Prachi Garg (was: Akmal Chaudhri) Prachi, I have reviewed and edited the doc pages. Please review when you have time. Thank you. > Add documentation for partition based dataset (release 2.5) > --- > > Key: IGNITE-8271 > URL: https://issues.apache.org/jira/browse/IGNITE-8271 > Project: Ignite > Issue Type: Improvement > Components: documentation, ml >Affects Versions: 2.5 >Reporter: Anton Dmitriev >Assignee: Prachi Garg >Priority: Major > Fix For: 2.5 > > > In Apache Ignite 2.5 we have added new infrastructure layer - partition based > dataset, so now we need to add correspondent documentation. > Affected pages: > [Machine > Learning|https://apacheignite.readme.io/v2.4/docs/machine-learning-25] > [Partition Based > Dataset|https://apacheignite.readme.io/v2.4/docs/partition-based-dataset-25] > In release 2.5 > [https://apacheignite.readme.io/docs/machine-learning|https://apacheignite.readme.io/docs/machine-learning] > page should be changed to > [https://apacheignite.readme.io/docs/machine-learning-25|https://apacheignite.readme.io/docs/machine-learning-25]. > In release 2.5 > [https://apacheignite.readme.io/docs/partition-based-dataset-25|https://apacheignite.readme.io/docs/partition-based-dataset-25] > page should be added. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-8269) Add documentation for decision tree (release 2.5)
[ https://issues.apache.org/jira/browse/IGNITE-8269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akmal Chaudhri reassigned IGNITE-8269: -- Assignee: Prachi Garg (was: Akmal Chaudhri) Prachi, I have reviewed and edited the doc page. Please review when you have time. Thank you. > Add documentation for decision tree (release 2.5) > - > > Key: IGNITE-8269 > URL: https://issues.apache.org/jira/browse/IGNITE-8269 > Project: Ignite > Issue Type: Improvement > Components: documentation, ml >Affects Versions: 2.5 >Reporter: Anton Dmitriev >Assignee: Prachi Garg >Priority: Major > Fix For: 2.5 > > > In Apache Ignite 2.5 we have added a decision tree based on partition based > dataset and now we need to documentation for this feature. > Affected pages: > [Decision Tree|https://apacheignite.readme.io/v2.4/docs/decision-tree-25] > In release 2.5 > [https://apacheignite.readme.io/docs/decision-trees|https://apacheignite.readme.io/docs/decision-trees] > page should be changed to > [https://apacheignite.readme.io/docs/decision-tree-25|https://apacheignite.readme.io/docs/decision-tree-25]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-8350) GA Grid: Prepare documentation for 2.5
[ https://issues.apache.org/jira/browse/IGNITE-8350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akmal Chaudhri reassigned IGNITE-8350: -- Assignee: Prachi Garg (was: Akmal Chaudhri) Prachi, I have reviewed and edited the doc page. Please review when you have time. Thank you. > GA Grid: Prepare documentation for 2.5 > -- > > Key: IGNITE-8350 > URL: https://issues.apache.org/jira/browse/IGNITE-8350 > Project: Ignite > Issue Type: New Feature > Components: documentation >Reporter: Turik Campbell >Assignee: Prachi Garg >Priority: Minor > Fix For: 2.5 > > > Review documentation and prepare for 2.5. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7912) control.sh script should show used WAL-segments
[ https://issues.apache.org/jira/browse/IGNITE-7912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16461273#comment-16461273 ] Ivan Daschinskiy commented on IGNITE-7912: -- Merged latest changes and added newest TC build. Tests seems to be ok. > control.sh script should show used WAL-segments > --- > > Key: IGNITE-7912 > URL: https://issues.apache.org/jira/browse/IGNITE-7912 > Project: Ignite > Issue Type: Improvement >Reporter: Sergey Filatov >Assignee: Ivan Daschinskiy >Priority: Minor > > We have to erase wal archive because wal archive can grow large and we must > have safe way to remove unused segments to free disk space. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-6429) GridCachePreloadingEvictionsSelfTest.testEvictions test fails periodically
[ https://issues.apache.org/jira/browse/IGNITE-6429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Pereslegin reassigned IGNITE-6429: Assignee: Pavel Pereslegin > GridCachePreloadingEvictionsSelfTest.testEvictions test fails periodically > --- > > Key: IGNITE-6429 > URL: https://issues.apache.org/jira/browse/IGNITE-6429 > Project: Ignite > Issue Type: Bug >Reporter: Andrey Gura >Assignee: Pavel Pereslegin >Priority: Major > Labels: MakeTeamcityGreenAgain > > {{GridCachePreloadingEvictionsSelfTest.testEvictions}} test fails > periodically. > {noformat} > [2017-09-18 15:35:03,054][ERROR][main][root] Test failed. > java.lang.AssertionError: Sizes do not match [s1=5136, s2=5159] > at > org.apache.ignite.internal.processors.cache.GridCachePreloadingEvictionsSelfTest.checkCachesConsistency(GridCachePreloadingEvictionsSelfTest.java:243) > at > org.apache.ignite.internal.processors.cache.GridCachePreloadingEvictionsSelfTest.testEvictions(GridCachePreloadingEvictionsSelfTest.java:162) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at junit.framework.TestCase.runTest(TestCase.java:176) > at > org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000) > at > org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132) > at > org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915) > at java.lang.Thread.run(Thread.java:745) > {noformat} > After fix test should be unmuted on TC. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8385) SQL: Allow variable-length values in index leafs
[ https://issues.apache.org/jira/browse/IGNITE-8385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16461844#comment-16461844 ] Joel Lang commented on IGNITE-8385: --- I did not realize there were situations where the actual indexed value would not be stored in the index itself. This might explain a great deal of the performance issue I had when using random UUID string indexes with a HDD. While the string contains a UUID that is not an actual requirement, so I can't change the data type to use the java UUID class, yet. After looking through the code I see CacheConfiguration has the max inline size option that I'm going to try raising to 36 to fit a complete UUID string. > SQL: Allow variable-length values in index leafs > > > Key: IGNITE-8385 > URL: https://issues.apache.org/jira/browse/IGNITE-8385 > Project: Ignite > Issue Type: Task > Components: sql >Affects Versions: 2.4 >Reporter: Vladimir Ozerov >Priority: Major > Labels: iep-19, performance > Fix For: 2.6 > > > Currently we have a restriction that every entry inside a BTree leaf should > be of fixed size. This restriction is artificial and prevents efficient index > usage because we have to choose so-called {{inline size}} for every index > manually. This is OK for fixed-size numeric types. But this could be a > problem for varlen types such as {{VARCHAR}} because in some cases we cannot > fit the whole value and have to fallback to data page lookup. In other cases > we may pick too pessimistic inline size value and index space would be > wasted. > What we need to do is to allow arbitrary item size in index pages. In this > case we would be able to inline all necessary values into index pages in most > cases. > Please pay attention that we may still met page overflow in case too long > data types are used. To mitigate this we should: > 1) Implement IGNITE-6055 first so that we can distinguish between limited and > unlimited data types. > 2) Unlimited data types should be inlined only partially > 3) We need to have special handling for too long rows (probably just re-use > existing logic with minimal adjustments) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8428) Web Console: Support connect to secured cluster
Alexey Kuznetsov created IGNITE-8428: Summary: Web Console: Support connect to secured cluster Key: IGNITE-8428 URL: https://issues.apache.org/jira/browse/IGNITE-8428 Project: Ignite Issue Type: Bug Components: wizards Reporter: Alexey Kuznetsov See: https://stackoverflow.com/questions/50065120/how-to-add-security-to-run-ignite-web-console-in-k8s -- This message was sent by Atlassian JIRA (v7.6.3#76005)