[jira] [Updated] (IGNITE-14285) sqllline: `Bad history file syntax!'
[
https://issues.apache.org/jira/browse/IGNITE-14285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Kasnacheev updated IGNITE-14285:
-
Fix Version/s: (was: 2.10.1)
2.10
> sqllline: `Bad history file syntax!'
>
>
> Key: IGNITE-14285
> URL: https://issues.apache.org/jira/browse/IGNITE-14285
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.10
>Reporter: Ilya Kasnacheev
>Assignee: Maxim Muzafarov
>Priority: Critical
> Fix For: 2.10
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When starting the updated sqlline in 2.10, I can see the following error
> message:
> {code}
> ~/Downloads/2.10/apache-ignite-slim-2.10.0-bin% bin/sqlline.sh
> мар 05, 2021 12:30:46 PM org.jline.utils.Log logr
> WARNING: Failed to load history
> java.lang.IllegalArgumentException: Bad history file syntax! The history file
> `/home/ikasnacheev/.sqlline/history` may be an older history: please remove
> it or use a different history file.
> at
> org.jline.reader.impl.history.DefaultHistory.addHistoryLine(DefaultHistory.java:185)
> at
> org.jline.reader.impl.history.DefaultHistory.addHistoryLine(DefaultHistory.java:169)
> at
> org.jline.reader.impl.history.DefaultHistory.lambda$load$0(DefaultHistory.java:86)
> at java.util.Iterator.forEachRemaining(Iterator.java:116)
> at
> java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801)
> at
> java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:647)
> at
> org.jline.reader.impl.history.DefaultHistory.load(DefaultHistory.java:86)
> at
> org.jline.reader.impl.history.DefaultHistory.attach(DefaultHistory.java:69)
> at sqlline.SqlLine.getConsoleReader(SqlLine.java:618)
> at sqlline.SqlLine.begin(SqlLine.java:511)
> at sqlline.SqlLine.start(SqlLine.java:267)
> at sqlline.SqlLine.main(SqlLine.java:206)
> {code}
> Moreover, if I remove the file, and run some command, then the old sqlline
> will use the history incorrectly:
> {code}
> sqlline version 1.3.0
> sqlline> 1614936870022:select * from person;
> {code}
> This is going to be a problem for all Ignite developers who use more than one
> version of Ignite on the same box, e.g. the entire development community.
> I recommend changing the default history file location to e.g.
> ~/.sqlline/apache-ignite.history.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14285) sqllline: `Bad history file syntax!'
[
https://issues.apache.org/jira/browse/IGNITE-14285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17296148#comment-17296148
]
Ilya Kasnacheev commented on IGNITE-14285:
--
LGTM for the shell script part.
> sqllline: `Bad history file syntax!'
>
>
> Key: IGNITE-14285
> URL: https://issues.apache.org/jira/browse/IGNITE-14285
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.10
>Reporter: Ilya Kasnacheev
>Assignee: Maxim Muzafarov
>Priority: Critical
> Fix For: 2.10.1
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When starting the updated sqlline in 2.10, I can see the following error
> message:
> {code}
> ~/Downloads/2.10/apache-ignite-slim-2.10.0-bin% bin/sqlline.sh
> мар 05, 2021 12:30:46 PM org.jline.utils.Log logr
> WARNING: Failed to load history
> java.lang.IllegalArgumentException: Bad history file syntax! The history file
> `/home/ikasnacheev/.sqlline/history` may be an older history: please remove
> it or use a different history file.
> at
> org.jline.reader.impl.history.DefaultHistory.addHistoryLine(DefaultHistory.java:185)
> at
> org.jline.reader.impl.history.DefaultHistory.addHistoryLine(DefaultHistory.java:169)
> at
> org.jline.reader.impl.history.DefaultHistory.lambda$load$0(DefaultHistory.java:86)
> at java.util.Iterator.forEachRemaining(Iterator.java:116)
> at
> java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801)
> at
> java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:647)
> at
> org.jline.reader.impl.history.DefaultHistory.load(DefaultHistory.java:86)
> at
> org.jline.reader.impl.history.DefaultHistory.attach(DefaultHistory.java:69)
> at sqlline.SqlLine.getConsoleReader(SqlLine.java:618)
> at sqlline.SqlLine.begin(SqlLine.java:511)
> at sqlline.SqlLine.start(SqlLine.java:267)
> at sqlline.SqlLine.main(SqlLine.java:206)
> {code}
> Moreover, if I remove the file, and run some command, then the old sqlline
> will use the history incorrectly:
> {code}
> sqlline version 1.3.0
> sqlline> 1614936870022:select * from person;
> {code}
> This is going to be a problem for all Ignite developers who use more than one
> version of Ignite on the same box, e.g. the entire development community.
> I recommend changing the default history file location to e.g.
> ~/.sqlline/apache-ignite.history.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14285) sqllline: `Bad history file syntax!'
[
https://issues.apache.org/jira/browse/IGNITE-14285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17296147#comment-17296147
]
Ilya Kasnacheev commented on IGNITE-14285:
--
It will still provide error message, but will read and write correct file. I
think it's OK for now.
> sqllline: `Bad history file syntax!'
>
>
> Key: IGNITE-14285
> URL: https://issues.apache.org/jira/browse/IGNITE-14285
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.10
>Reporter: Ilya Kasnacheev
>Assignee: Maxim Muzafarov
>Priority: Critical
> Fix For: 2.10.1
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When starting the updated sqlline in 2.10, I can see the following error
> message:
> {code}
> ~/Downloads/2.10/apache-ignite-slim-2.10.0-bin% bin/sqlline.sh
> мар 05, 2021 12:30:46 PM org.jline.utils.Log logr
> WARNING: Failed to load history
> java.lang.IllegalArgumentException: Bad history file syntax! The history file
> `/home/ikasnacheev/.sqlline/history` may be an older history: please remove
> it or use a different history file.
> at
> org.jline.reader.impl.history.DefaultHistory.addHistoryLine(DefaultHistory.java:185)
> at
> org.jline.reader.impl.history.DefaultHistory.addHistoryLine(DefaultHistory.java:169)
> at
> org.jline.reader.impl.history.DefaultHistory.lambda$load$0(DefaultHistory.java:86)
> at java.util.Iterator.forEachRemaining(Iterator.java:116)
> at
> java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801)
> at
> java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:647)
> at
> org.jline.reader.impl.history.DefaultHistory.load(DefaultHistory.java:86)
> at
> org.jline.reader.impl.history.DefaultHistory.attach(DefaultHistory.java:69)
> at sqlline.SqlLine.getConsoleReader(SqlLine.java:618)
> at sqlline.SqlLine.begin(SqlLine.java:511)
> at sqlline.SqlLine.start(SqlLine.java:267)
> at sqlline.SqlLine.main(SqlLine.java:206)
> {code}
> Moreover, if I remove the file, and run some command, then the old sqlline
> will use the history incorrectly:
> {code}
> sqlline version 1.3.0
> sqlline> 1614936870022:select * from person;
> {code}
> This is going to be a problem for all Ignite developers who use more than one
> version of Ignite on the same box, e.g. the entire development community.
> I recommend changing the default history file location to e.g.
> ~/.sqlline/apache-ignite.history.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14284) sqlline: `Property "url" is required'
[
https://issues.apache.org/jira/browse/IGNITE-14284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17296144#comment-17296144
]
Ilya Kasnacheev commented on IGNITE-14284:
--
I don't think that we need it at all. I will remove it.
> sqlline: `Property "url" is required'
> -
>
> Key: IGNITE-14284
> URL: https://issues.apache.org/jira/browse/IGNITE-14284
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.10
>Reporter: Ilya Kasnacheev
>Priority: Major
> Labels: sqlline
>
> Currently, when you run sqlline.sh, the following output is shown:
> {code}
> ~/Downloads/2.10/apache-ignite-slim-2.10.0-bin% bin/sqlline.sh
> Property "url" is required
> sqlline version 1.9.0
> sqlline>
> {code}
> We did not have this confusing warning when using sqlline 1.3.0. From this
> on, it will work as expected, with !connect jdbc:ignite:thin://localhost, etc.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14284) sqlline: `Property "url" is required'
[
https://issues.apache.org/jira/browse/IGNITE-14284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17296101#comment-17296101
]
Ilya Kasnacheev commented on IGNITE-14284:
--
Do we really need to specify -d Driver in case when we already supply the
correct classpath? I will check it.
> sqlline: `Property "url" is required'
> -
>
> Key: IGNITE-14284
> URL: https://issues.apache.org/jira/browse/IGNITE-14284
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.10
>Reporter: Ilya Kasnacheev
>Priority: Major
> Labels: sqlline
>
> Currently, when you run sqlline.sh, the following output is shown:
> {code}
> ~/Downloads/2.10/apache-ignite-slim-2.10.0-bin% bin/sqlline.sh
> Property "url" is required
> sqlline version 1.9.0
> sqlline>
> {code}
> We did not have this confusing warning when using sqlline 1.3.0. From this
> on, it will work as expected, with !connect jdbc:ignite:thin://localhost, etc.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14285) sqllline: `Bad history file syntax!'
[
https://issues.apache.org/jira/browse/IGNITE-14285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17296098#comment-17296098
]
Ilya Kasnacheev commented on IGNITE-14285:
--
Looks OK, have you tried it on Windows though? I will try to check it in
practice.
> sqllline: `Bad history file syntax!'
>
>
> Key: IGNITE-14285
> URL: https://issues.apache.org/jira/browse/IGNITE-14285
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.10
>Reporter: Ilya Kasnacheev
>Assignee: Maxim Muzafarov
>Priority: Critical
> Fix For: 2.10.1
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When starting the updated sqlline in 2.10, I can see the following error
> message:
> {code}
> ~/Downloads/2.10/apache-ignite-slim-2.10.0-bin% bin/sqlline.sh
> мар 05, 2021 12:30:46 PM org.jline.utils.Log logr
> WARNING: Failed to load history
> java.lang.IllegalArgumentException: Bad history file syntax! The history file
> `/home/ikasnacheev/.sqlline/history` may be an older history: please remove
> it or use a different history file.
> at
> org.jline.reader.impl.history.DefaultHistory.addHistoryLine(DefaultHistory.java:185)
> at
> org.jline.reader.impl.history.DefaultHistory.addHistoryLine(DefaultHistory.java:169)
> at
> org.jline.reader.impl.history.DefaultHistory.lambda$load$0(DefaultHistory.java:86)
> at java.util.Iterator.forEachRemaining(Iterator.java:116)
> at
> java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801)
> at
> java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:647)
> at
> org.jline.reader.impl.history.DefaultHistory.load(DefaultHistory.java:86)
> at
> org.jline.reader.impl.history.DefaultHistory.attach(DefaultHistory.java:69)
> at sqlline.SqlLine.getConsoleReader(SqlLine.java:618)
> at sqlline.SqlLine.begin(SqlLine.java:511)
> at sqlline.SqlLine.start(SqlLine.java:267)
> at sqlline.SqlLine.main(SqlLine.java:206)
> {code}
> Moreover, if I remove the file, and run some command, then the old sqlline
> will use the history incorrectly:
> {code}
> sqlline version 1.3.0
> sqlline> 1614936870022:select * from person;
> {code}
> This is going to be a problem for all Ignite developers who use more than one
> version of Ignite on the same box, e.g. the entire development community.
> I recommend changing the default history file location to e.g.
> ~/.sqlline/apache-ignite.history.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14215) Website: Enable Lucky Orange and Yandex Metrics
[ https://issues.apache.org/jira/browse/IGNITE-14215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17296029#comment-17296029 ] Denis A. Magda commented on IGNITE-14215: - [~mstekl] thanks! We won't need Lucky Orange after the audit is over but I would keep Yandex Metrica because it shows heatmaps and other metrics unsupported by Google Metrics. Let's add Yandex Metrica support permanently by adding it to upcoming/future releases of the APIs and technical docs. Ignite 2.10 is coming (check the dev list), so I would implement it for that release and following. > Website: Enable Lucky Orange and Yandex Metrics > --- > > Key: IGNITE-14215 > URL: https://issues.apache.org/jira/browse/IGNITE-14215 > Project: Ignite > Issue Type: Bug > Components: website >Reporter: Denis A. Magda >Assignee: Mauricio Stekl >Priority: Major > > We're conducting a usability audit of the Ignite website to better understand > what parts of the site get more attention and what doesn't resonate with > developers landing on the pages. The goal is to introduce and explain Ignite > in the most concise and technical way, and to guide the users from the > landing pages to documentation and other pages so that they can transition > with their Ignite journey seamlessly. > > To better understand how the users perceive the information on the current > web pages, we need to see heatmaps and other advanced metrics that are > supported by the following tools: > * [https://www.luckyorange.com|https://www.luckyorange.com/] > * [https://metrica.yandex.com/about]? > Let's use the tools for the time of the audit. All the data is capture and > kept anonymous. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14285) sqllline: `Bad history file syntax!'
[
https://issues.apache.org/jira/browse/IGNITE-14285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-14285:
-
Fix Version/s: (was: 2.11)
2.10.1
> sqllline: `Bad history file syntax!'
>
>
> Key: IGNITE-14285
> URL: https://issues.apache.org/jira/browse/IGNITE-14285
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.10
>Reporter: Ilya Kasnacheev
>Assignee: Maxim Muzafarov
>Priority: Critical
> Fix For: 2.10.1
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When starting the updated sqlline in 2.10, I can see the following error
> message:
> {code}
> ~/Downloads/2.10/apache-ignite-slim-2.10.0-bin% bin/sqlline.sh
> мар 05, 2021 12:30:46 PM org.jline.utils.Log logr
> WARNING: Failed to load history
> java.lang.IllegalArgumentException: Bad history file syntax! The history file
> `/home/ikasnacheev/.sqlline/history` may be an older history: please remove
> it or use a different history file.
> at
> org.jline.reader.impl.history.DefaultHistory.addHistoryLine(DefaultHistory.java:185)
> at
> org.jline.reader.impl.history.DefaultHistory.addHistoryLine(DefaultHistory.java:169)
> at
> org.jline.reader.impl.history.DefaultHistory.lambda$load$0(DefaultHistory.java:86)
> at java.util.Iterator.forEachRemaining(Iterator.java:116)
> at
> java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801)
> at
> java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:647)
> at
> org.jline.reader.impl.history.DefaultHistory.load(DefaultHistory.java:86)
> at
> org.jline.reader.impl.history.DefaultHistory.attach(DefaultHistory.java:69)
> at sqlline.SqlLine.getConsoleReader(SqlLine.java:618)
> at sqlline.SqlLine.begin(SqlLine.java:511)
> at sqlline.SqlLine.start(SqlLine.java:267)
> at sqlline.SqlLine.main(SqlLine.java:206)
> {code}
> Moreover, if I remove the file, and run some command, then the old sqlline
> will use the history incorrectly:
> {code}
> sqlline version 1.3.0
> sqlline> 1614936870022:select * from person;
> {code}
> This is going to be a problem for all Ignite developers who use more than one
> version of Ignite on the same box, e.g. the entire development community.
> I recommend changing the default history file location to e.g.
> ~/.sqlline/apache-ignite.history.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-14285) sqllline: `Bad history file syntax!'
[
https://issues.apache.org/jira/browse/IGNITE-14285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov reassigned IGNITE-14285:
Fix Version/s: 2.11
Assignee: Maxim Muzafarov
> sqllline: `Bad history file syntax!'
>
>
> Key: IGNITE-14285
> URL: https://issues.apache.org/jira/browse/IGNITE-14285
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.10
>Reporter: Ilya Kasnacheev
>Assignee: Maxim Muzafarov
>Priority: Critical
> Fix For: 2.11
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When starting the updated sqlline in 2.10, I can see the following error
> message:
> {code}
> ~/Downloads/2.10/apache-ignite-slim-2.10.0-bin% bin/sqlline.sh
> мар 05, 2021 12:30:46 PM org.jline.utils.Log logr
> WARNING: Failed to load history
> java.lang.IllegalArgumentException: Bad history file syntax! The history file
> `/home/ikasnacheev/.sqlline/history` may be an older history: please remove
> it or use a different history file.
> at
> org.jline.reader.impl.history.DefaultHistory.addHistoryLine(DefaultHistory.java:185)
> at
> org.jline.reader.impl.history.DefaultHistory.addHistoryLine(DefaultHistory.java:169)
> at
> org.jline.reader.impl.history.DefaultHistory.lambda$load$0(DefaultHistory.java:86)
> at java.util.Iterator.forEachRemaining(Iterator.java:116)
> at
> java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801)
> at
> java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:647)
> at
> org.jline.reader.impl.history.DefaultHistory.load(DefaultHistory.java:86)
> at
> org.jline.reader.impl.history.DefaultHistory.attach(DefaultHistory.java:69)
> at sqlline.SqlLine.getConsoleReader(SqlLine.java:618)
> at sqlline.SqlLine.begin(SqlLine.java:511)
> at sqlline.SqlLine.start(SqlLine.java:267)
> at sqlline.SqlLine.main(SqlLine.java:206)
> {code}
> Moreover, if I remove the file, and run some command, then the old sqlline
> will use the history incorrectly:
> {code}
> sqlline version 1.3.0
> sqlline> 1614936870022:select * from person;
> {code}
> This is going to be a problem for all Ignite developers who use more than one
> version of Ignite on the same box, e.g. the entire development community.
> I recommend changing the default history file location to e.g.
> ~/.sqlline/apache-ignite.history.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-14285) sqllline: `Bad history file syntax!'
[
https://issues.apache.org/jira/browse/IGNITE-14285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17296024#comment-17296024
]
Maxim Muzafarov edited comment on IGNITE-14285 at 3/5/21, 1:42 PM:
---
[~ilyak]
Please, take a look at the patch I provided.
was (Author: mmuzaf):
[~ilyak]
Please, take a look.
> sqllline: `Bad history file syntax!'
>
>
> Key: IGNITE-14285
> URL: https://issues.apache.org/jira/browse/IGNITE-14285
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.10
>Reporter: Ilya Kasnacheev
>Assignee: Maxim Muzafarov
>Priority: Critical
> Fix For: 2.11
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When starting the updated sqlline in 2.10, I can see the following error
> message:
> {code}
> ~/Downloads/2.10/apache-ignite-slim-2.10.0-bin% bin/sqlline.sh
> мар 05, 2021 12:30:46 PM org.jline.utils.Log logr
> WARNING: Failed to load history
> java.lang.IllegalArgumentException: Bad history file syntax! The history file
> `/home/ikasnacheev/.sqlline/history` may be an older history: please remove
> it or use a different history file.
> at
> org.jline.reader.impl.history.DefaultHistory.addHistoryLine(DefaultHistory.java:185)
> at
> org.jline.reader.impl.history.DefaultHistory.addHistoryLine(DefaultHistory.java:169)
> at
> org.jline.reader.impl.history.DefaultHistory.lambda$load$0(DefaultHistory.java:86)
> at java.util.Iterator.forEachRemaining(Iterator.java:116)
> at
> java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801)
> at
> java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:647)
> at
> org.jline.reader.impl.history.DefaultHistory.load(DefaultHistory.java:86)
> at
> org.jline.reader.impl.history.DefaultHistory.attach(DefaultHistory.java:69)
> at sqlline.SqlLine.getConsoleReader(SqlLine.java:618)
> at sqlline.SqlLine.begin(SqlLine.java:511)
> at sqlline.SqlLine.start(SqlLine.java:267)
> at sqlline.SqlLine.main(SqlLine.java:206)
> {code}
> Moreover, if I remove the file, and run some command, then the old sqlline
> will use the history incorrectly:
> {code}
> sqlline version 1.3.0
> sqlline> 1614936870022:select * from person;
> {code}
> This is going to be a problem for all Ignite developers who use more than one
> version of Ignite on the same box, e.g. the entire development community.
> I recommend changing the default history file location to e.g.
> ~/.sqlline/apache-ignite.history.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14285) sqllline: `Bad history file syntax!'
[
https://issues.apache.org/jira/browse/IGNITE-14285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17296024#comment-17296024
]
Maxim Muzafarov commented on IGNITE-14285:
--
[~ilyak]
Please, take a look.
> sqllline: `Bad history file syntax!'
>
>
> Key: IGNITE-14285
> URL: https://issues.apache.org/jira/browse/IGNITE-14285
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.10
>Reporter: Ilya Kasnacheev
>Assignee: Maxim Muzafarov
>Priority: Critical
> Fix For: 2.11
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When starting the updated sqlline in 2.10, I can see the following error
> message:
> {code}
> ~/Downloads/2.10/apache-ignite-slim-2.10.0-bin% bin/sqlline.sh
> мар 05, 2021 12:30:46 PM org.jline.utils.Log logr
> WARNING: Failed to load history
> java.lang.IllegalArgumentException: Bad history file syntax! The history file
> `/home/ikasnacheev/.sqlline/history` may be an older history: please remove
> it or use a different history file.
> at
> org.jline.reader.impl.history.DefaultHistory.addHistoryLine(DefaultHistory.java:185)
> at
> org.jline.reader.impl.history.DefaultHistory.addHistoryLine(DefaultHistory.java:169)
> at
> org.jline.reader.impl.history.DefaultHistory.lambda$load$0(DefaultHistory.java:86)
> at java.util.Iterator.forEachRemaining(Iterator.java:116)
> at
> java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801)
> at
> java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:647)
> at
> org.jline.reader.impl.history.DefaultHistory.load(DefaultHistory.java:86)
> at
> org.jline.reader.impl.history.DefaultHistory.attach(DefaultHistory.java:69)
> at sqlline.SqlLine.getConsoleReader(SqlLine.java:618)
> at sqlline.SqlLine.begin(SqlLine.java:511)
> at sqlline.SqlLine.start(SqlLine.java:267)
> at sqlline.SqlLine.main(SqlLine.java:206)
> {code}
> Moreover, if I remove the file, and run some command, then the old sqlline
> will use the history incorrectly:
> {code}
> sqlline version 1.3.0
> sqlline> 1614936870022:select * from person;
> {code}
> This is going to be a problem for all Ignite developers who use more than one
> version of Ignite on the same box, e.g. the entire development community.
> I recommend changing the default history file location to e.g.
> ~/.sqlline/apache-ignite.history.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14170) Adding metrics of using WAL archive
[ https://issues.apache.org/jira/browse/IGNITE-14170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17296021#comment-17296021 ] Kirill Tkalenko commented on IGNITE-14170: -- [~sergeychugunov] Fresh build: https://ci.ignite.apache.org/viewLog.html?buildId=5902944=IgniteTests24Java8_BuildApacheIgnite > Adding metrics of using WAL archive > --- > > Key: IGNITE-14170 > URL: https://issues.apache.org/jira/browse/IGNITE-14170 > Project: Ignite > Issue Type: Improvement > Components: persistence >Reporter: Kirill Tkalenko >Assignee: Kirill Tkalenko >Priority: Major > Fix For: 2.11 > > Time Spent: 20m > Remaining Estimate: 0h > > At the moment there is no way to estimate how many segments in the archive we > may need, for example, per day. It is proposed to add the following metrics: > * The number of bytes logged to the WAL; > * The number of compressed bytes in the WAL. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14170) Adding metrics of using WAL archive
[ https://issues.apache.org/jira/browse/IGNITE-14170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17296019#comment-17296019 ] Sergey Chugunov commented on IGNITE-14170: -- [~ktkale...@gridgain.com], Patch looks good to me. > Adding metrics of using WAL archive > --- > > Key: IGNITE-14170 > URL: https://issues.apache.org/jira/browse/IGNITE-14170 > Project: Ignite > Issue Type: Improvement > Components: persistence >Reporter: Kirill Tkalenko >Assignee: Kirill Tkalenko >Priority: Major > Fix For: 2.11 > > Time Spent: 20m > Remaining Estimate: 0h > > At the moment there is no way to estimate how many segments in the archive we > may need, for example, per day. It is proposed to add the following metrics: > * The number of bytes logged to the WAL; > * The number of compressed bytes in the WAL. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14284) sqlline: `Property "url" is required'
[
https://issues.apache.org/jira/browse/IGNITE-14284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17296013#comment-17296013
]
Maxim Muzafarov commented on IGNITE-14284:
--
[~ilyak]
I don't think we can change something here. According to the [1] commit do not
have the "URL" command-line property simultaneously with setting {{-d Driver}}
was an issue which has been fixed in 1.7.0 [2].
[1]
https://github.com/julianhyde/sqlline/pull/236/files#diff-cb4a4540820da130c7309afccffe53450738acaf77ab35ab346d1c8b18da0d23R408
[2] https://github.com/julianhyde/sqlline/blob/master/HISTORY.md#170-2019-03-27
> sqlline: `Property "url" is required'
> -
>
> Key: IGNITE-14284
> URL: https://issues.apache.org/jira/browse/IGNITE-14284
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.10
>Reporter: Ilya Kasnacheev
>Priority: Major
> Labels: sqlline
>
> Currently, when you run sqlline.sh, the following output is shown:
> {code}
> ~/Downloads/2.10/apache-ignite-slim-2.10.0-bin% bin/sqlline.sh
> Property "url" is required
> sqlline version 1.9.0
> sqlline>
> {code}
> We did not have this confusing warning when using sqlline 1.3.0. From this
> on, it will work as expected, with !connect jdbc:ignite:thin://localhost, etc.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14276) Local maven build runs tests while they are switched off by skipTests option
[
https://issues.apache.org/jira/browse/IGNITE-14276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17296004#comment-17296004
]
Vyacheslav Koptilin commented on IGNITE-14276:
--
Hi [~vveider],
Merged to the main branch. Thank you for the contribution!
> Local maven build runs tests while they are switched off by skipTests option
>
>
> Key: IGNITE-14276
> URL: https://issues.apache.org/jira/browse/IGNITE-14276
> Project: Ignite
> Issue Type: Bug
>Reporter: Andrey N. Gura
>Assignee: Peter Ivanov
>Priority: Major
> Fix For: 3.0.0-alpha2
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Local maven build runs unit-tests in despite of skipTests option.
> {code}
> mvn clean install -DskipTests
> {code}
> Expected behavior: build procedure will compile tests but will not run tests.
> Actual behavior: build procedure runs tests.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14187) .NET Thin Client: DataStreamer
[ https://issues.apache.org/jira/browse/IGNITE-14187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17296003#comment-17296003 ] Aleksey Plekhanov commented on IGNITE-14187: [~ptupitsyn] I have only local benchmark results (from my laptop), and in these results streamer works almost with the same performance as putAll (BTW, for thick client performance is about the same). I think these results are not very relevant and benchmarks should be made on a real cluster. > .NET Thin Client: DataStreamer > -- > > Key: IGNITE-14187 > URL: https://issues.apache.org/jira/browse/IGNITE-14187 > Project: Ignite > Issue Type: New Feature > Components: platforms, thin client >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Labels: .NET, iep-68 > Fix For: 2.11 > > Time Spent: 10m > Remaining Estimate: 0h > > Add data streaming to Thin Client -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-14151) Set up commit status publisher on TC
[ https://issues.apache.org/jira/browse/IGNITE-14151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Ivanov closed IGNITE-14151. - > Set up commit status publisher on TC > > > Key: IGNITE-14151 > URL: https://issues.apache.org/jira/browse/IGNITE-14151 > Project: Ignite > Issue Type: Task >Reporter: Valentin Kulichenko >Assignee: Peter Ivanov >Priority: Major > Labels: teamcity > Attachments: Screenshot 2021-03-04 at 13.03.25.png > > Time Spent: 35m > Remaining Estimate: 0h > > 'Run All' build should publish the status to the appropriate PR on GitHub. We > will then update the process to allow merges only with successful builds. > See here: https://www.jetbrains.com/help/teamcity/commit-status-publisher.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14281) Calcite. Colocated tables are considered non colocated
[ https://issues.apache.org/jira/browse/IGNITE-14281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Orlov updated IGNITE-14281: -- Summary: Calcite. Colocated tables are considered non colocated (was: Calcite. Colocated tables considered non colocated) > Calcite. Colocated tables are considered non colocated > -- > > Key: IGNITE-14281 > URL: https://issues.apache.org/jira/browse/IGNITE-14281 > Project: Ignite > Issue Type: Bug > Components: sql >Reporter: Konstantin Orlov >Assignee: Konstantin Orlov >Priority: Major > > Currently distribution trait for replicated cache is built over 0th column > which is _KEY column. Because of this a colocated join is considered > non-colocated until _KEY columns is not used explicitly as join predicate. > Need to fix this. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-13912) Incorrect calculation of WAL segments that should be deleted from WAL archive
[ https://issues.apache.org/jira/browse/IGNITE-13912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17295966#comment-17295966 ] shivakumar edited comment on IGNITE-13912 at 3/5/21, 10:45 AM: --- Hi [~ktkale...@gridgain.com] I do not have much idea on Ignite source code, I am new to Ignite code, I will try to understand the code to debug the issue from my side, could you please give any reference to the unit test scenario of reserving a WAL segment by PME or releasing an unwanted WAL segment. If you can share any links which explain the design of WAL segment cleanup and WAL segment reservation for PME would be helpful in understanding the code. Is it ok, If the reproducer launches 3 instances of Ignite nodes on a windows machine and starts ingesting data to reproduce the issue? Thanks, Shiva was (Author: shm): Hi [~ktkale...@gridgain.com] I do not have much idea on Ignite source code, I am new to Ignite code, I will try to understand the code, could you please give any reference to the unit test scenario of reserving a WAL segment by PME or releasing an unwanted WAL segment. If you can share any links which explain the design of WAL segment cleanup and WAL segment reservation for PME would be helpful in understanding the code. Is it ok, If the reproducer launches 3 instances of Ignite nodes on a windows machine and starts ingesting data to reproduce the issue? Thanks, Shiva > Incorrect calculation of WAL segments that should be deleted from WAL archive > - > > Key: IGNITE-13912 > URL: https://issues.apache.org/jira/browse/IGNITE-13912 > Project: Ignite > Issue Type: Bug > Components: persistence >Reporter: Kirill Tkalenko >Assignee: Kirill Tkalenko >Priority: Critical > Fix For: 2.10 > > Attachments: config.properties, ignite-config, reproducer.zip, > server1-full-wal-checkpoint.log, wal-checkpoint-logs, wal_dir_contents, > wal_grows_from_peak.PNG, wal_issue_reproduced.PNG, wal_usage.PNG, > wal_usage_dec12.PNG, wal_usage_dec22nd_binary.PNG > > Time Spent: 40m > Remaining Estimate: 0h > > Now there is an incorrect calculation of WAL segments that should be deleted > from WAL archive. Since we delete only those segments whose total size should > not exceed *DataStorageConfiguration#maxWalArchiveSize * > IGNITE_THRESHOLD_WAL_ARCHIVE_SIZE_PERCENTAGE*, but should be up to > DataStorageConfiguration#maxWalArchiveSize * > IGNITE_THRESHOLD_WAL_ARCHIVE_SIZE_PERCENTAGE*. Therefore, an excess of > *DataStorageConfiguration#maxWalArchiveSize* occurs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13912) Incorrect calculation of WAL segments that should be deleted from WAL archive
[ https://issues.apache.org/jira/browse/IGNITE-13912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17295966#comment-17295966 ] shivakumar commented on IGNITE-13912: - Hi [~ktkale...@gridgain.com] I do not have much idea on Ignite source code, I am new to Ignite code, I will try to understand the code, could you please give any reference to the unit test scenario of reserving a WAL segment by PME or releasing an unwanted WAL segment. If you can share any links which explain the design of WAL segment cleanup and WAL segment reservation for PME would be helpful in understanding the code. Is it ok, If the reproducer launches 3 instances of Ignite nodes on a windows machine and starts ingesting data to reproduce the issue? Thanks, Shiva > Incorrect calculation of WAL segments that should be deleted from WAL archive > - > > Key: IGNITE-13912 > URL: https://issues.apache.org/jira/browse/IGNITE-13912 > Project: Ignite > Issue Type: Bug > Components: persistence >Reporter: Kirill Tkalenko >Assignee: Kirill Tkalenko >Priority: Critical > Fix For: 2.10 > > Attachments: config.properties, ignite-config, reproducer.zip, > server1-full-wal-checkpoint.log, wal-checkpoint-logs, wal_dir_contents, > wal_grows_from_peak.PNG, wal_issue_reproduced.PNG, wal_usage.PNG, > wal_usage_dec12.PNG, wal_usage_dec22nd_binary.PNG > > Time Spent: 40m > Remaining Estimate: 0h > > Now there is an incorrect calculation of WAL segments that should be deleted > from WAL archive. Since we delete only those segments whose total size should > not exceed *DataStorageConfiguration#maxWalArchiveSize * > IGNITE_THRESHOLD_WAL_ARCHIVE_SIZE_PERCENTAGE*, but should be up to > DataStorageConfiguration#maxWalArchiveSize * > IGNITE_THRESHOLD_WAL_ARCHIVE_SIZE_PERCENTAGE*. Therefore, an excess of > *DataStorageConfiguration#maxWalArchiveSize* occurs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14285) sqllline: `Bad history file syntax!'
[
https://issues.apache.org/jira/browse/IGNITE-14285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Kasnacheev updated IGNITE-14285:
-
Description:
When starting the updated sqlline in 2.10, I can see the following error
message:
{code}
~/Downloads/2.10/apache-ignite-slim-2.10.0-bin% bin/sqlline.sh
мар 05, 2021 12:30:46 PM org.jline.utils.Log logr
WARNING: Failed to load history
java.lang.IllegalArgumentException: Bad history file syntax! The history file
`/home/ikasnacheev/.sqlline/history` may be an older history: please remove it
or use a different history file.
at
org.jline.reader.impl.history.DefaultHistory.addHistoryLine(DefaultHistory.java:185)
at
org.jline.reader.impl.history.DefaultHistory.addHistoryLine(DefaultHistory.java:169)
at
org.jline.reader.impl.history.DefaultHistory.lambda$load$0(DefaultHistory.java:86)
at java.util.Iterator.forEachRemaining(Iterator.java:116)
at
java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801)
at
java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:647)
at
org.jline.reader.impl.history.DefaultHistory.load(DefaultHistory.java:86)
at
org.jline.reader.impl.history.DefaultHistory.attach(DefaultHistory.java:69)
at sqlline.SqlLine.getConsoleReader(SqlLine.java:618)
at sqlline.SqlLine.begin(SqlLine.java:511)
at sqlline.SqlLine.start(SqlLine.java:267)
at sqlline.SqlLine.main(SqlLine.java:206)
{code}
Moreover, if I remove the file, and run some command, then the old sqlline will
use the history incorrectly:
{code}
sqlline version 1.3.0
sqlline> 1614936870022:select * from person;
{code}
This is going to be a problem for all Ignite developers who use more than one
version of Ignite on the same box, e.g. the entire development community.
I recommend changing the default history file location to e.g.
~/.sqlline/apache-ignite.history.
was:
When starting the updated sqlline in 2.10, I can see the following error
message:
{code}
~/Downloads/2.10/apache-ignite-slim-2.10.0-bin% bin/sqlline.sh
мар 05, 2021 12:30:46 PM org.jline.utils.Log logr
WARNING: Failed to load history
java.lang.IllegalArgumentException: Bad history file syntax! The history file
`/home/ikasnacheev/.sqlline/history` may be an older history: please remove it
or use a different history file.
at
org.jline.reader.impl.history.DefaultHistory.addHistoryLine(DefaultHistory.java:185)
at
org.jline.reader.impl.history.DefaultHistory.addHistoryLine(DefaultHistory.java:169)
at
org.jline.reader.impl.history.DefaultHistory.lambda$load$0(DefaultHistory.java:86)
at java.util.Iterator.forEachRemaining(Iterator.java:116)
at
java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801)
at
java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:647)
at
org.jline.reader.impl.history.DefaultHistory.load(DefaultHistory.java:86)
at
org.jline.reader.impl.history.DefaultHistory.attach(DefaultHistory.java:69)
at sqlline.SqlLine.getConsoleReader(SqlLine.java:618)
at sqlline.SqlLine.begin(SqlLine.java:511)
at sqlline.SqlLine.start(SqlLine.java:267)
at sqlline.SqlLine.main(SqlLine.java:206)
{code}
Moreover, if I remove the file, and run some command, then the old sqlline will
use the history incorrectly:
{code}
sqlline version 1.3.0
sqlline> 1614936870022:select * from person;
{code}
This is going to be a problem for all Ignite developers who use more than one
version of Ignite on the same box, e.g. the entirely development community.
I recommend changing the default history file location to e.g.
~/.sqlline/apache-ignite.history.
> sqllline: `Bad history file syntax!'
>
>
> Key: IGNITE-14285
> URL: https://issues.apache.org/jira/browse/IGNITE-14285
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.10
>Reporter: Ilya Kasnacheev
>Priority: Critical
>
> When starting the updated sqlline in 2.10, I can see the following error
> message:
> {code}
> ~/Downloads/2.10/apache-ignite-slim-2.10.0-bin% bin/sqlline.sh
> мар 05, 2021 12:30:46 PM org.jline.utils.Log logr
> WARNING: Failed to load history
> java.lang.IllegalArgumentException: Bad history file syntax! The history file
> `/home/ikasnacheev/.sqlline/history` may be an older history: please remove
> it or use a different history file.
> at
> org.jline.reader.impl.history.DefaultHistory.addHistoryLine(DefaultHistory.java:185)
> at
> org.jline.reader.impl.history.DefaultHistory.addHistoryLine(DefaultHistory.java:169)
> at
> org.jline.reader.impl.history.DefaultHistory.lambda$load$0(DefaultHistory.java:86)
> at
[jira] [Created] (IGNITE-14285) sqllline: `Bad history file syntax!'
Ilya Kasnacheev created IGNITE-14285:
Summary: sqllline: `Bad history file syntax!'
Key: IGNITE-14285
URL: https://issues.apache.org/jira/browse/IGNITE-14285
Project: Ignite
Issue Type: Bug
Affects Versions: 2.10
Reporter: Ilya Kasnacheev
When starting the updated sqlline in 2.10, I can see the following error
message:
{code}
~/Downloads/2.10/apache-ignite-slim-2.10.0-bin% bin/sqlline.sh
мар 05, 2021 12:30:46 PM org.jline.utils.Log logr
WARNING: Failed to load history
java.lang.IllegalArgumentException: Bad history file syntax! The history file
`/home/ikasnacheev/.sqlline/history` may be an older history: please remove it
or use a different history file.
at
org.jline.reader.impl.history.DefaultHistory.addHistoryLine(DefaultHistory.java:185)
at
org.jline.reader.impl.history.DefaultHistory.addHistoryLine(DefaultHistory.java:169)
at
org.jline.reader.impl.history.DefaultHistory.lambda$load$0(DefaultHistory.java:86)
at java.util.Iterator.forEachRemaining(Iterator.java:116)
at
java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801)
at
java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:647)
at
org.jline.reader.impl.history.DefaultHistory.load(DefaultHistory.java:86)
at
org.jline.reader.impl.history.DefaultHistory.attach(DefaultHistory.java:69)
at sqlline.SqlLine.getConsoleReader(SqlLine.java:618)
at sqlline.SqlLine.begin(SqlLine.java:511)
at sqlline.SqlLine.start(SqlLine.java:267)
at sqlline.SqlLine.main(SqlLine.java:206)
{code}
Moreover, if I remove the file, and run some command, then the old sqlline will
use the history incorrectly:
{code}
sqlline version 1.3.0
sqlline> 1614936870022:select * from person;
{code}
This is going to be a problem for all Ignite developers who use more than one
version of Ignite on the same box, e.g. the entirely development community.
I recommend changing the default history file location to e.g.
~/.sqlline/apache-ignite.history.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14284) sqlline: `Property "url" is required'
Ilya Kasnacheev created IGNITE-14284:
Summary: sqlline: `Property "url" is required'
Key: IGNITE-14284
URL: https://issues.apache.org/jira/browse/IGNITE-14284
Project: Ignite
Issue Type: Bug
Affects Versions: 2.10
Reporter: Ilya Kasnacheev
Currently, when you run sqlline.sh, the following output is shown:
{code}
~/Downloads/2.10/apache-ignite-slim-2.10.0-bin% bin/sqlline.sh
Property "url" is required
sqlline version 1.9.0
sqlline>
{code}
We did not have this confusing warning when using sqlline 1.3.0. From this on,
it will work as expected, with !connect jdbc:ignite:thin://localhost, etc.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14259) Ducktests pre-merge presentation
[ https://issues.apache.org/jira/browse/IGNITE-14259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-14259: -- Sprint: Ducktape Sprint 4, Ducktape Sprint 5 (was: Ducktape Sprint 4) > Ducktests pre-merge presentation > > > Key: IGNITE-14259 > URL: https://issues.apache.org/jira/browse/IGNITE-14259 > Project: Ignite > Issue Type: Bug >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > > A webinar-like presentation is required to discuss what we got before the > merge. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14023) Password based authentication support in ducktape tests
[
https://issues.apache.org/jira/browse/IGNITE-14023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-14023:
--
Sprint: Ducktape Sprint 1, Ducktape Sprint 2, Ducktape Sprint 3, Ducktape
Sprint 4, Ducktape Sprint 5 (was: Ducktape Sprint 1, Ducktape Sprint 2,
Ducktape Sprint 3, Ducktape Sprint 4)
> Password based authentication support in ducktape tests
> ---
>
> Key: IGNITE-14023
> URL: https://issues.apache.org/jira/browse/IGNITE-14023
> Project: Ignite
> Issue Type: Task
>Reporter: Mikhail Filatov
>Assignee: Mikhail Filatov
>Priority: Minor
> Time Spent: 9h 20m
> Remaining Estimate: 0h
>
> There are users with authentication enabled on the cluster
> Ducktape tests should work on such clusters.
> Tests should work if authentication is enabled on the cluster via a
> third-party plugin
> Running Ignite node and application with third-party authentication plugin
> remains to be implemented by the developers of that plugin.
> In this PR we will only implement the ability to tell control.sh how to
> connect to the cluster.
> connection parameters should be passed through globals with structure like
> that.
> {
> "use_ssl": True,
> "admin": {
> "credentials": ["username", "qwerty_123"],
> "ssl": {
> "key_store_jks":
> }
> }
> }
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14226) Ducktape test of rebalance
[ https://issues.apache.org/jira/browse/IGNITE-14226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-14226: -- Sprint: Ducktape Sprint 4, Ducktape Sprint 5 (was: Ducktape Sprint 4) > Ducktape test of rebalance > -- > > Key: IGNITE-14226 > URL: https://issues.apache.org/jira/browse/IGNITE-14226 > Project: Ignite > Issue Type: Test >Reporter: Dmitriy Sorokin >Assignee: Dmitriy Sorokin >Priority: Major > > The test should check the rebalance on both in-memory caches and persistent > caches. > In case of persistent caches, the test also should check both modes of > rebalance: full and historical (asserts is needed that the proper mode of > rebalance was worked). > Basic scenario: > Testing of rebalance triggered by two event types: node enter and node leave > (baseline change in persistent mode). > Extended scenario: > Node entering or leaving during rebalance process. > Test parameters: > # Initial node count; > # Cache count; > # Cache entry count; > # Cache entry size; > # Mode: in-memory or persistence; > # Rebalance trigger event: node enter or node leave. > Test result: time taken to rebalance process. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13969) Thin client test [umbrella]
[ https://issues.apache.org/jira/browse/IGNITE-13969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-13969: -- Sprint: Ducktape Sprint 1, Ducktape Sprint 2, Ducktape Sprint 3, Ducktape Sprint 4, Ducktape Sprint 5 (was: Ducktape Sprint 1, Ducktape Sprint 2, Ducktape Sprint 3, Ducktape Sprint 4) > Thin client test [umbrella] > --- > > Key: IGNITE-13969 > URL: https://issues.apache.org/jira/browse/IGNITE-13969 > Project: Ignite > Issue Type: Wish >Reporter: Anton Vinogradov >Assignee: Evgeniya Vdovets >Priority: Major > > Ensure Thin client works. > Check the whole TC API. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14137) Detect and fix failures reasons (nightly runs fails)
[ https://issues.apache.org/jira/browse/IGNITE-14137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-14137: -- Sprint: Ducktape Sprint 3, Ducktape Sprint 4, Ducktape Sprint 5 (was: Ducktape Sprint 3, Ducktape Sprint 4) > Detect and fix failures reasons (nightly runs fails) > > > Key: IGNITE-14137 > URL: https://issues.apache.org/jira/browse/IGNITE-14137 > Project: Ignite > Issue Type: Bug >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Blocker > > Jenkins runs fails, 1-4 ... 60 tests affected. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14258) Ducktests code de-duplication and simplification
[ https://issues.apache.org/jira/browse/IGNITE-14258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-14258: -- Sprint: Ducktape Sprint 4, Ducktape Sprint 5 (was: Ducktape Sprint 4) > Ducktests code de-duplication and simplification > > > Key: IGNITE-14258 > URL: https://issues.apache.org/jira/browse/IGNITE-14258 > Project: Ignite > Issue Type: Bug >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Major > > The goal is to perform pre-merge review of the whole ducktests code and > refactor it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14275) SQL. Calcite: MapReduce aggregates for hash distribution
[ https://issues.apache.org/jira/browse/IGNITE-14275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17295889#comment-17295889 ] Yury Gerzhedovich commented on IGNITE-14275: [~tledkov-gridgain], Could you please review? > SQL. Calcite: MapReduce aggregates for hash distribution > > > Key: IGNITE-14275 > URL: https://issues.apache.org/jira/browse/IGNITE-14275 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Yury Gerzhedovich >Assignee: Yury Gerzhedovich >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Currently, we don't choice map-reduce aggregates algorithm for hash > distribution, also the same issue there is for aggregates which could used > with no GROUP BY clouse like a COUNT function. > Need to implement this possibility. -- This message was sent by Atlassian Jira (v8.3.4#803005)
