[jira] [Comment Edited] (IGNITE-6065) Quick way to find broken documentation links
[
https://issues.apache.org/jira/browse/IGNITE-6065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16178550#comment-16178550
]
Ilya Borisov edited comment on IGNITE-6065 at 9/25/17 5:34 AM:
---
I've decided to go with a script instead of a unit test because it was easier
to implement and won't require any additional changes to CI setup. You have to
run it manually from _modules/webconsole/frontend/scripts/check-doc-links_. Run
with _--help_ parameter for usage info. The script requires at least Node.js
8.5.0.
Output example:
{code}
> node scripts\check-doc-links.js
Looking for invalid apacheignite.readme.io domain doc links in
./{app,views}/**/*.pug.
Checking links [===] 35/35
Total links: 35
Invalid links found: 1
1. https://apacheignite.readme.io/docsss/data-grid in
./app/modules/states/configuration/caches/general.pug
{code}
[~kuaw26] please review.
was (Author: klaster_1):
I've decided to go with a script instead of a unit test because it was easier
to implement and won't require any additional changes to CI setup. You have to
run it manually from _modules/webconsole/frontend/scripts/check-doc-links_. Run
with _--help_ parameter for usage info.
Output example:
{code}
> node scripts\check-doc-links.js
Looking for invalid apacheignite.readme.io domain doc links in
./{app,views}/**/*.pug.
Checking links [===] 35/35
Total links: 35
Invalid links found: 1
1. https://apacheignite.readme.io/docsss/data-grid in
./app/modules/states/configuration/caches/general.pug
{code}
[~kuaw26] please review.
> Quick way to find broken documentation links
>
>
> Key: IGNITE-6065
> URL: https://issues.apache.org/jira/browse/IGNITE-6065
> Project: Ignite
> Issue Type: Test
> Components: UI, wizards
>Reporter: Ilya Borisov
>Assignee: Ilya Borisov
>Priority: Minor
> Attachments: configuration more info link.PNG
>
>
> Documentation links break from time to time. We need a tool that walks all
> links and reports anything we might want to fix. Since all links are in .pug
> templates, I suggest to use pug-walk from standard pug package.
> The tool should:
> 1. Provide a way to change location of pug files and docs domain name
> (apacheignite.readme.io by default).
> 2. If invalid link are found, output a list of link / pug path.
> 3. Provide usage info in some way (readme or --help argument).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (IGNITE-6065) Quick way to find broken documentation links
[
https://issues.apache.org/jira/browse/IGNITE-6065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16178550#comment-16178550
]
Ilya Borisov edited comment on IGNITE-6065 at 9/25/17 5:32 AM:
---
I've decided to go with a script instead of a unit test because it was easier
to implement and won't require any additional changes to CI setup. You have to
run it manually from _modules/webconsole/frontend/scripts/check-doc-links_. Run
with _--help_ parameter for usage info.
Output example:
{code}
> node scripts\check-doc-links.js
Looking for invalid apacheignite.readme.io domain doc links in
./{app,views}/**/*.pug.
Checking links [===] 35/35
Total links: 35
Invalid links found: 1
1. https://apacheignite.readme.io/docsss/data-grid in
./app/modules/states/configuration/caches/general.pug
{code}
[~kuaw26] please review.
was (Author: klaster_1):
I've decided to go with a script instead of a unit test because it was easier
to implement and won't require any additional changes to CI setup. You have to
run it manually from _modules/webconsole/frontend/scripts/check-doc-links_. Use
_--help_ for usage info.
Output example:
{code}
> node scripts\check-doc-links.js
Looking for invalid apacheignite.readme.io domain doc links in
./{app,views}/**/*.pug.
Checking links [===] 35/35
Total links: 35
Invalid links found: 1
1. https://apacheignite.readme.io/docsss/data-grid in
./app/modules/states/configuration/caches/general.pug
{code}
[~kuaw26] please review.
> Quick way to find broken documentation links
>
>
> Key: IGNITE-6065
> URL: https://issues.apache.org/jira/browse/IGNITE-6065
> Project: Ignite
> Issue Type: Test
> Components: UI, wizards
>Reporter: Ilya Borisov
>Assignee: Ilya Borisov
>Priority: Minor
> Attachments: configuration more info link.PNG
>
>
> Documentation links break from time to time. We need a tool that walks all
> links and reports anything we might want to fix. Since all links are in .pug
> templates, I suggest to use pug-walk from standard pug package.
> The tool should:
> 1. Provide a way to change location of pug files and docs domain name
> (apacheignite.readme.io by default).
> 2. If invalid link are found, output a list of link / pug path.
> 3. Provide usage info in some way (readme or --help argument).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-6065) Quick way to find broken documentation links
[
https://issues.apache.org/jira/browse/IGNITE-6065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16178550#comment-16178550
]
Ilya Borisov commented on IGNITE-6065:
--
I've decided to go with a script instead of a unit test because it was easier
to implement and won't require any additional changes to CI setup. You have to
run it manually from _modules/webconsole/frontend/scripts/check-doc-links_. Use
_--help_ for usage info.
Output example:
{code}
> node scripts\check-doc-links.js
Looking for invalid apacheignite.readme.io domain doc links in
./{app,views}/**/*.pug.
Checking links [===] 35/35
Total links: 35
Invalid links found: 1
1. https://apacheignite.readme.io/docsss/data-grid in
./app/modules/states/configuration/caches/general.pug
{code}
[~kuaw26] please review.
> Quick way to find broken documentation links
>
>
> Key: IGNITE-6065
> URL: https://issues.apache.org/jira/browse/IGNITE-6065
> Project: Ignite
> Issue Type: Test
> Components: UI, wizards
>Reporter: Ilya Borisov
>Assignee: Ilya Borisov
>Priority: Minor
> Attachments: configuration more info link.PNG
>
>
> Documentation links break from time to time. We need a tool that walks all
> links and reports anything we might want to fix. Since all links are in .pug
> templates, I suggest to use pug-walk from standard pug package.
> The tool should:
> 1. Provide a way to change location of pug files and docs domain name
> (apacheignite.readme.io by default).
> 2. If invalid link are found, output a list of link / pug path.
> 3. Provide usage info in some way (readme or --help argument).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (IGNITE-6222) Adapt Linear regression for distributed environment
[ https://issues.apache.org/jira/browse/IGNITE-6222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ALEKSEY ZINOVEV reassigned IGNITE-6222: --- Assignee: ALEKSEY ZINOVEV (was: Yury Babak) > Adapt Linear regression for distributed environment > --- > > Key: IGNITE-6222 > URL: https://issues.apache.org/jira/browse/IGNITE-6222 > Project: Ignite > Issue Type: Bug > Components: ml >Reporter: Yury Babak >Assignee: ALEKSEY ZINOVEV > Fix For: 2.3 > > > Currently our implementation of linear regression works only locally which is > useless. So we need fix this implementation. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (IGNITE-6065) Quick way to find broken documentation links
[ https://issues.apache.org/jira/browse/IGNITE-6065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov updated IGNITE-6065: - Description: Documentation links break from time to time. We need a tool that walks all links and reports anything we might want to fix. Since all links are in .pug templates, I suggest to use pug-walk from standard pug package. The tool should: 1. Provide a way to change location of pug files and docs domain name (apacheignite.readme.io by default). 2. If invalid link are found, output a list of link / pug path. 3. Provide usage info in some way (readme or --help argument). was:Documentation links break from time to time. We need a special test that walks all links and reports anything we might want to fix. Since all links are in .pug templates, I suggest to use pug-walk from standard pug package. > Quick way to find broken documentation links > > > Key: IGNITE-6065 > URL: https://issues.apache.org/jira/browse/IGNITE-6065 > Project: Ignite > Issue Type: Test > Components: UI, wizards >Reporter: Ilya Borisov >Assignee: Ilya Borisov >Priority: Minor > Attachments: configuration more info link.PNG > > > Documentation links break from time to time. We need a tool that walks all > links and reports anything we might want to fix. Since all links are in .pug > templates, I suggest to use pug-walk from standard pug package. > The tool should: > 1. Provide a way to change location of pug files and docs domain name > (apacheignite.readme.io by default). > 2. If invalid link are found, output a list of link / pug path. > 3. Provide usage info in some way (readme or --help argument). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-6053) IgniteCache.clear clears local caches with same names on all server nodes
[ https://issues.apache.org/jira/browse/IGNITE-6053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16178505#comment-16178505 ] ASF GitHub Bot commented on IGNITE-6053: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/2443 > IgniteCache.clear clears local caches with same names on all server nodes > - > > Key: IGNITE-6053 > URL: https://issues.apache.org/jira/browse/IGNITE-6053 > Project: Ignite > Issue Type: Bug >Affects Versions: 1.7 >Reporter: Evgenii Zhuravlev >Assignee: Roman Shtykh > Fix For: 2.3 > > > Clear on LOCAL cache should clear cache on the current node only, not on all > nodes, that have local caches with same names. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-6490) Optimize log search speed
Alexey Kuznetsov created IGNITE-6490: Summary: Optimize log search speed Key: IGNITE-6490 URL: https://issues.apache.org/jira/browse/IGNITE-6490 Project: Ignite Issue Type: Improvement Components: wizards Affects Versions: 2.1 Reporter: Alexey Kuznetsov Assignee: Vasiliy Sisko Fix For: 2.3 I see in VisorLogSearchJob code like this: `if (s.toLowerCase().contains(searchStr))` and this is very non effective. This can be reworked to `regionMatches` and this job should be profiled and may be some other optimizations can be implemented. See similar issue on SO: https://codereview.stackexchange.com/questions/44021/fast-way-of-searching-for-a-string-in-a-text-file -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (IGNITE-5767) Web console: use byte array type instead of java.lang.Object for binary JDBC types
[
https://issues.apache.org/jira/browse/IGNITE-5767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vasiliy Sisko reassigned IGNITE-5767:
-
Assignee: Vasiliy Sisko (was: Andrey Novikov)
> Web console: use byte array type instead of java.lang.Object for binary JDBC
> types
> --
>
> Key: IGNITE-5767
> URL: https://issues.apache.org/jira/browse/IGNITE-5767
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Denis Kholodov
>Assignee: Vasiliy Sisko
> Fix For: 2.3
>
>
> Schema importer should use {{[B}} query entity field type instead of
> {{java.lang.Object}} for the following SQL types: {{BINARY}}, {{VARBINARY}}
> and {{LONGVARBINARY}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (IGNITE-6059) Use any distributed matrix in K-Means
[
https://issues.apache.org/jira/browse/IGNITE-6059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16178182#comment-16178182
]
Oleg Ignatenko edited comment on IGNITE-6059 at 9/24/17 12:51 PM:
--
[~mlipkovich] the answer to your question is _no_ and, _maybe_, see below.
_No_ - because [current interface of this
clusterer|https://github.com/apache/ignite/blob/master/modules/ml/src/main/java/org/apache/ignite/ml/clustering/KMeansDistributedClusterer.java|
see it at Ignite master on Github] explicitly requires sparse distributed
matrix:
{code}KMeansDistributedClusterer extends
BaseKMeansClusterer{code}
_Maybe_ - because when I gave it a quick try and changed class and method
signatures to use AbstractMatrix instead of SparseDistributedMatrix compiler
didn't complain.
A way to ensure if this replacement is legitimate that comes to mind is to
replicate currently existing unit tests and examples involving this clusterer
to similar code that uses some other implementation of AbstractMatrix and
verify that these pass.
was (Author: oignatenko):
[~mlipkovich] the answer to your question is _no_ and, _maybe_, see below.
_No_ - because current interface of this clusterer explicitly requires sparse
distributed matrix:
{code}KMeansDistributedClusterer extends
BaseKMeansClusterer{code}
_Maybe_ - because when I gave it a quick try and changed class and method
signatures to use AbstractMatrix instead of SparseDistributedMatrix compiler
didn't complain.
A way to ensure if this replacement is legitimate that comes to mind is to
replicate currently existing unit tests and examples involving this clusterer
to similar code that uses some other implementation of AbstractMatrix and
verify that these pass.
> Use any distributed matrix in K-Means
> -
>
> Key: IGNITE-6059
> URL: https://issues.apache.org/jira/browse/IGNITE-6059
> Project: Ignite
> Issue Type: Improvement
> Components: ml
>Reporter: Yury Babak
> Fix For: 2.3
>
>
> Currently k-means work only with row/col matrix.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (IGNITE-6059) Use any distributed matrix in K-Means
[
https://issues.apache.org/jira/browse/IGNITE-6059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16178182#comment-16178182
]
Oleg Ignatenko commented on IGNITE-6059:
[~mlipkovich] the answer to your question is _no_ and, _maybe_, see below.
_No_ - because current interface of this clusterer explicitly requires sparse
distributed matrix:
{code}KMeansDistributedClusterer extends
BaseKMeansClusterer{code}
_Maybe_ - because when I gave it a quick try and changed class and method
signatures to use AbstractMatrix instead of SparseDistributedMatrix compiler
didn't complain.
A way to ensure if this replacement is legitimate that comes to mind is to
replicate currently existing unit tests and examples involving this clusterer
to similar code that uses some other implementation of AbstractMatrix and
verify that these pass.
> Use any distributed matrix in K-Means
> -
>
> Key: IGNITE-6059
> URL: https://issues.apache.org/jira/browse/IGNITE-6059
> Project: Ignite
> Issue Type: Improvement
> Components: ml
>Reporter: Yury Babak
> Fix For: 2.3
>
>
> Currently k-means work only with row/col matrix.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (IGNITE-6123) First performance measurement of implemented ml algorithms
[ https://issues.apache.org/jira/browse/IGNITE-6123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16135591#comment-16135591 ] Oleg Ignatenko edited comment on IGNITE-6123 at 9/24/17 12:31 PM: -- Making it based on standard Ignite benchmarking framework ([Yardstick|https://github.com/apache/ignite/tree/master/modules/yardstick]). Work in progress ([branch ignite-6123|https://github.com/gridgain/apache-ignite/tree/ignite-6123]): currently implemented benchmarks for KMeansLocalClusterer and KMeansDistributedClusterer. was (Author: oignatenko): plan to make it based on standard Ignite benchmarking framework ([Yardstick|https://github.com/apache/ignite/tree/master/modules/yardstick]) > First performance measurement of implemented ml algorithms > -- > > Key: IGNITE-6123 > URL: https://issues.apache.org/jira/browse/IGNITE-6123 > Project: Ignite > Issue Type: Improvement > Components: ml >Reporter: Yury Babak >Assignee: Oleg Ignatenko > Fix For: 2.3 > > > We want to start tracking our performance to avoid performance degradation. > Also we need some performance comparison with other ml libs. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-6059) Use any distributed matrix in K-Means
[ https://issues.apache.org/jira/browse/IGNITE-6059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16178169#comment-16178169 ] Yury Babak commented on IGNITE-6059: Hi Mikhail, Actually we have two implementations of k-means, local and distributed and this ticket about distributed version. Currently distributed k-means works with SparseDistributedMatrix wich is row/col based. But we also have SparseBlockDistributedMatrix. So main goal of this ticket is support SparseBlockDistributedMatrix for distributed version of k-means and main challenge is keep performance on the same level as of SparseDistributedMatrix. For me this sounds difficult, on the other hand I double-checked other tickets and this one look like the easiest for a newbie. So if you want to join us - welcome. Btw, as far as I know [~oignatenko] works on benchmark related ticket(IGNITE-6123) and if would like to start with this, contact with him about performance measurement. I look forward to your commits. Regards, Yury > Use any distributed matrix in K-Means > - > > Key: IGNITE-6059 > URL: https://issues.apache.org/jira/browse/IGNITE-6059 > Project: Ignite > Issue Type: Improvement > Components: ml >Reporter: Yury Babak > Fix For: 2.3 > > > Currently k-means work only with row/col matrix. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (IGNITE-6222) Adapt Linear regression for distributed environment
[ https://issues.apache.org/jira/browse/IGNITE-6222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Babak reassigned IGNITE-6222: -- Assignee: Yury Babak > Adapt Linear regression for distributed environment > --- > > Key: IGNITE-6222 > URL: https://issues.apache.org/jira/browse/IGNITE-6222 > Project: Ignite > Issue Type: Bug > Components: ml >Reporter: Yury Babak >Assignee: Yury Babak > Fix For: 2.3 > > > Currently our implementation of linear regression works only locally which is > useless. So we need fix this implementation. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (IGNITE-6222) Adapt Linear regression for distributed environment
[ https://issues.apache.org/jira/browse/IGNITE-6222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yury Babak reassigned IGNITE-6222: -- Assignee: (was: Yury Babak) > Adapt Linear regression for distributed environment > --- > > Key: IGNITE-6222 > URL: https://issues.apache.org/jira/browse/IGNITE-6222 > Project: Ignite > Issue Type: Bug > Components: ml >Reporter: Yury Babak > Fix For: 2.3 > > > Currently our implementation of linear regression works only locally which is > useless. So we need fix this implementation. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (IGNITE-5979) [Test Failed] GridCacheAtomicInvalidPartitionHandlingSelfTest.testPrimaryFullAsync
[
https://issues.apache.org/jira/browse/IGNITE-5979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16178124#comment-16178124
]
Vadim Opolski commented on IGNITE-5979:
---
Hi [~sboikov], [~avinogradov] As I can see, test is failing approximately in
20% of runs. The reason of failure is not matching entry value in local and
backup nodes. It looks like affinity function didn't complete and additional
timeout is needed. Could you please advice, where extra timeout might be needed?
> [Test Failed]
> GridCacheAtomicInvalidPartitionHandlingSelfTest.testPrimaryFullAsync
>
>
> Key: IGNITE-5979
> URL: https://issues.apache.org/jira/browse/IGNITE-5979
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Eduard Shangareev
>Assignee: Vadim Opolski
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.3
>
>
> Example of failing -
> http://ci.ignite.apache.org/viewLog.html?buildId=760709=buildResultsDiv=Ignite20Tests_IgniteDataGridFailover#testNameId6248548165747570497
> {noformat}
> junit.framework.AssertionFailedError: Failed to check value for key
> [key=72625, node=0671e5c8-8bd5-4f2a-b1b8-9e945742, primary=false,
> recNodeId=101770ef-a622-4f7c-b714-70ecf1f1] expected:<0> but
> was:<-1994497644>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.TestCase.assertEquals(TestCase.java:244)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridCacheAtomicInvalidPartitionHandlingSelfTest.checkRestarts(GridCacheAtomicInvalidPartitionHandlingSelfTest.java:334)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridCacheAtomicInvalidPartitionHandlingSelfTest.testPrimaryFullAsync(GridCacheAtomicInvalidPartitionHandlingSelfTest.java:154)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
