[jira] [Comment Edited] (IGNITE-11593) python thin client: insert and select VARBINARY data type through SQL
[
https://issues.apache.org/jira/browse/IGNITE-11593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17317761#comment-17317761
]
Ivan Daschinsky edited comment on IGNITE-11593 at 4/9/21, 8:05 AM:
---
On recent version all works ok
{code:python}
from pyignite import Client
import pyignite
print(pyignite.__version__)
client = Client()
client.connect('127.0.0.1', 10800)
client.sql('DROP TABLE test IF EXISTS')
client.sql('CREATE TABLE test(id int primary key, varbin VARBINARY)')
client.sql('INSERT INTO test(id, varbin) VALUES (?, ?)', query_args=(1,
bytearray('Test message', 'UTF-8')))
result = client.sql('SELECT * FROM test')
field_data = list(*result)
print(field_data)
...
0.4.0-dev
[1, bytearray(b'Test message')]
{code}
was (Author: ivandasch):
On recent version all works ok
{code: python}
from pyignite import Client
import pyignite
print(pyignite.__version__)
client = Client()
client.connect('127.0.0.1', 10800)
client.sql('DROP TABLE test IF EXISTS')
client.sql('CREATE TABLE test(id int primary key, varbin VARBINARY)')
client.sql('INSERT INTO test(id, varbin) VALUES (?, ?)', query_args=(1,
bytearray('Test message', 'UTF-8')))
result = client.sql('SELECT * FROM test')
field_data = list(*result)
print(field_data)
...
0.4.0-dev
[1, bytearray(b'Test message')]
{code}
> python thin client: insert and select VARBINARY data type through SQL
> -
>
> Key: IGNITE-11593
> URL: https://issues.apache.org/jira/browse/IGNITE-11593
> Project: Ignite
> Issue Type: Bug
> Components: thin client
>Affects Versions: 2.7
>Reporter: Stepan Pilschikov
>Assignee: Dmitry Melnichuk
>Priority: Major
> Labels: python
>
> varbin data type select is getting not parsed array of integer values
> Example:
> https://gist.github.com/pilshchikov/b98ce5514209ef7009099b9c188398a6
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-11593) python thin client: insert and select VARBINARY data type through SQL
[
https://issues.apache.org/jira/browse/IGNITE-11593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17317761#comment-17317761
]
Ivan Daschinsky edited comment on IGNITE-11593 at 4/9/21, 8:05 AM:
---
On recent version all works ok
{code: python}
from pyignite import Client
import pyignite
print(pyignite.__version__)
client = Client()
client.connect('127.0.0.1', 10800)
client.sql('DROP TABLE test IF EXISTS')
client.sql('CREATE TABLE test(id int primary key, varbin VARBINARY)')
client.sql('INSERT INTO test(id, varbin) VALUES (?, ?)', query_args=(1,
bytearray('Test message', 'UTF-8')))
result = client.sql('SELECT * FROM test')
field_data = list(*result)
print(field_data)
...
0.4.0-dev
[1, bytearray(b'Test message')]
{code}
was (Author: ivandasch):
On recent version all works ok
{code: python}
from pyignite import Client
import pyignite
print(pyignite.__version__)
client = Client()
client.connect('127.0.0.1', 10800)
client.sql('DROP TABLE test IF EXISTS')
client.sql('CREATE TABLE test(id int primary key, varbin VARBINARY)')
client.sql('INSERT INTO test(id, varbin) VALUES (?, ?)', query_args=(1,
bytearray('Test message', 'UTF-8')))
result = client.sql('SELECT * FROM test')
field_data = list(*result)
print(field_data)
...
0.4.0-dev
[1, bytearray(b'Test message')]
{code}
> python thin client: insert and select VARBINARY data type through SQL
> -
>
> Key: IGNITE-11593
> URL: https://issues.apache.org/jira/browse/IGNITE-11593
> Project: Ignite
> Issue Type: Bug
> Components: thin client
>Affects Versions: 2.7
>Reporter: Stepan Pilschikov
>Assignee: Dmitry Melnichuk
>Priority: Major
> Labels: python
>
> varbin data type select is getting not parsed array of integer values
> Example:
> https://gist.github.com/pilshchikov/b98ce5514209ef7009099b9c188398a6
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-11593) python thin client: insert and select VARBINARY data type through SQL
[
https://issues.apache.org/jira/browse/IGNITE-11593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17317761#comment-17317761
]
Ivan Daschinsky commented on IGNITE-11593:
--
On recent version all works ok
{code: python}
from pyignite import Client
import pyignite
print(pyignite.__version__)
client = Client()
client.connect('127.0.0.1', 10800)
client.sql('DROP TABLE test IF EXISTS')
client.sql('CREATE TABLE test(id int primary key, varbin VARBINARY)')
client.sql('INSERT INTO test(id, varbin) VALUES (?, ?)', query_args=(1,
bytearray('Test message', 'UTF-8')))
result = client.sql('SELECT * FROM test')
field_data = list(*result)
print(field_data)
...
0.4.0-dev
[1, bytearray(b'Test message')]
{code}
> python thin client: insert and select VARBINARY data type through SQL
> -
>
> Key: IGNITE-11593
> URL: https://issues.apache.org/jira/browse/IGNITE-11593
> Project: Ignite
> Issue Type: Bug
> Components: thin client
>Affects Versions: 2.7
>Reporter: Stepan Pilschikov
>Assignee: Dmitry Melnichuk
>Priority: Major
> Labels: python
>
> varbin data type select is getting not parsed array of integer values
> Example:
> https://gist.github.com/pilshchikov/b98ce5514209ef7009099b9c188398a6
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (IGNITE-11593) python thin client: insert and select VARBINARY data type through SQL
[ https://issues.apache.org/jira/browse/IGNITE-11593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Daschinsky resolved IGNITE-11593. -- Fix Version/s: python-0.4.0 Resolution: Fixed > python thin client: insert and select VARBINARY data type through SQL > - > > Key: IGNITE-11593 > URL: https://issues.apache.org/jira/browse/IGNITE-11593 > Project: Ignite > Issue Type: Bug > Components: thin client >Affects Versions: 2.7 >Reporter: Stepan Pilschikov >Assignee: Dmitry Melnichuk >Priority: Major > Labels: python > Fix For: python-0.4.0 > > > varbin data type select is getting not parsed array of integer values > Example: > https://gist.github.com/pilshchikov/b98ce5514209ef7009099b9c188398a6 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14509) [Ducktape: Thin client] SSL connection check
Evgeniya Vdovets created IGNITE-14509: - Summary: [Ducktape: Thin client] SSL connection check Key: IGNITE-14509 URL: https://issues.apache.org/jira/browse/IGNITE-14509 Project: Ignite Issue Type: Sub-task Reporter: Evgeniya Vdovets Need to check ssl connection for thin client — Task: modify thin client compatibility test (ignite-13970) - add input parameter to mark ssl/no ssl - create ClientConfig which contains addresses and port, data should be provided from py test - modify IgniteAwareService to use this config for thin clients -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-14509) [Ducktape: Thin client] SSL connection check
[ https://issues.apache.org/jira/browse/IGNITE-14509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgeniya Vdovets reassigned IGNITE-14509: - Assignee: Evgeniya Vdovets > [Ducktape: Thin client] SSL connection check > > > Key: IGNITE-14509 > URL: https://issues.apache.org/jira/browse/IGNITE-14509 > Project: Ignite > Issue Type: Sub-task >Reporter: Evgeniya Vdovets >Assignee: Evgeniya Vdovets >Priority: Major > > Need to check ssl connection for thin client > — > Task: modify thin client compatibility test (ignite-13970) > - add input parameter to mark ssl/no ssl > - create ClientConfig which contains addresses and port, data should be > provided from py test > - modify IgniteAwareService to use this config for thin clients -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-11593) python thin client: insert and select VARBINARY data type through SQL
[ https://issues.apache.org/jira/browse/IGNITE-11593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Daschinsky updated IGNITE-11593: - Labels: python thin (was: python) > python thin client: insert and select VARBINARY data type through SQL > - > > Key: IGNITE-11593 > URL: https://issues.apache.org/jira/browse/IGNITE-11593 > Project: Ignite > Issue Type: Bug > Components: thin client >Affects Versions: 2.7 >Reporter: Stepan Pilschikov >Assignee: Dmitry Melnichuk >Priority: Major > Labels: python, thin > Fix For: python-0.4.0 > > > varbin data type select is getting not parsed array of integer values > Example: > https://gist.github.com/pilshchikov/b98ce5514209ef7009099b9c188398a6 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14510) Document java thin client continuous queries
Aleksey Plekhanov created IGNITE-14510: -- Summary: Document java thin client continuous queries Key: IGNITE-14510 URL: https://issues.apache.org/jira/browse/IGNITE-14510 Project: Ignite Issue Type: Improvement Components: documentation Affects Versions: 2.11 Reporter: Aleksey Plekhanov Assignee: Aleksey Plekhanov Fix For: 2.11 The new feature was added by IGNITE-14402, documentation needed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-11593) python thin client: insert and select VARBINARY data type through SQL
[ https://issues.apache.org/jira/browse/IGNITE-11593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Daschinsky reassigned IGNITE-11593: Assignee: Ivan Daschinsky (was: Dmitry Melnichuk) > python thin client: insert and select VARBINARY data type through SQL > - > > Key: IGNITE-11593 > URL: https://issues.apache.org/jira/browse/IGNITE-11593 > Project: Ignite > Issue Type: Bug > Components: thin client >Affects Versions: 2.7 >Reporter: Stepan Pilschikov >Assignee: Ivan Daschinsky >Priority: Major > Labels: python, thin > Fix For: python-0.4.0 > > > varbin data type select is getting not parsed array of integer values > Example: > https://gist.github.com/pilshchikov/b98ce5514209ef7009099b9c188398a6 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-14404) Highlight that Ignite supports only Java 8 and 11
[ https://issues.apache.org/jira/browse/IGNITE-14404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Gusev reassigned IGNITE-14404: --- Assignee: Igor Gusev > Highlight that Ignite supports only Java 8 and 11 > - > > Key: IGNITE-14404 > URL: https://issues.apache.org/jira/browse/IGNITE-14404 > Project: Ignite > Issue Type: Improvement > Components: documentation >Reporter: Nikita Safonov >Assignee: Igor Gusev >Priority: Major > Labels: docuentation > Time Spent: 10m > Remaining Estimate: 0h > > We need to say that Ignite supports only Java 8 and Java 11. > The current doc implies that it supports Java 8+ > See the table here: > https://ignite.apache.org/docs/latest/quick-start/java#prerequisites -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14404) Highlight that Ignite supports only Java 8 and 11
[ https://issues.apache.org/jira/browse/IGNITE-14404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17317825#comment-17317825 ] Igor Gusev commented on IGNITE-14404: - [~dma...@apache.org] can you merge this update? > Highlight that Ignite supports only Java 8 and 11 > - > > Key: IGNITE-14404 > URL: https://issues.apache.org/jira/browse/IGNITE-14404 > Project: Ignite > Issue Type: Improvement > Components: documentation >Reporter: Nikita Safonov >Assignee: Igor Gusev >Priority: Major > Labels: docuentation > Time Spent: 10m > Remaining Estimate: 0h > > We need to say that Ignite supports only Java 8 and Java 11. > The current doc implies that it supports Java 8+ > See the table here: > https://ignite.apache.org/docs/latest/quick-start/java#prerequisites -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14428) Formalize the names of the metrics included in the metric registry.
[
https://issues.apache.org/jira/browse/IGNITE-14428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17317836#comment-17317836
]
Ignite TC Bot commented on IGNITE-14428:
{panel:title=Branch: [pull/8937/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8937/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5944058&buildTypeId=IgniteTests24Java8_RunAll]
> Formalize the names of the metrics included in the metric registry.
>
>
> Key: IGNITE-14428
> URL: https://issues.apache.org/jira/browse/IGNITE-14428
> Project: Ignite
> Issue Type: Improvement
>Reporter: Mikhail Petrov
>Assignee: Mikhail Petrov
>Priority: Major
> Labels: IEP-35
> Time Spent: 3h 20m
> Remaining Estimate: 0h
>
> It's needed to refactor metric names to obey the global rule - all of them
> must start with name of the registry they belongs to. And add corresponding
> assertion.
> The purpose of this change is to make all metrics that belongs to one
> MetricRegistry have the name that obeys mentioned above rule regardless how
> they were registered. It helps to use a consistent approach to work with all
> metrics.
> The following metric names will be changed to obey this rule:
> JoinedNodes -> io.discovery.JoinedNodes
> LeftNodes -> io.discovery.LeftNodes
> FailedNodes -> io.discovery.FailedNodes
> PendingMessagesRegistered -> io.discovery.PendingMessagesRegistered
> CommunicationErrors -> io.discovery.CommunicationErrors
> CurrentTopologyVersion -> io.discovery.CurrentTopologyVersion
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14509) [Ducktape: Thin client] XML-based configuration
[ https://issues.apache.org/jira/browse/IGNITE-14509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgeniya Vdovets updated IGNITE-14509: -- Summary: [Ducktape: Thin client] XML-based configuration (was: [Ducktape: Thin client] SSL connection check) > [Ducktape: Thin client] XML-based configuration > --- > > Key: IGNITE-14509 > URL: https://issues.apache.org/jira/browse/IGNITE-14509 > Project: Ignite > Issue Type: Sub-task >Reporter: Evgeniya Vdovets >Assignee: Evgeniya Vdovets >Priority: Major > > Need to check ssl connection for thin client > — > Task: modify thin client compatibility test (ignite-13970) > - add input parameter to mark ssl/no ssl > - create ClientConfig which contains addresses and port, data should be > provided from py test > - modify IgniteAwareService to use this config for thin clients -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14385) Add checkpoit information to performance statistics.
[
https://issues.apache.org/jira/browse/IGNITE-14385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17317854#comment-17317854
]
Ignite TC Bot commented on IGNITE-14385:
{panel:title=Branch: [pull/8928/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8928/head] Base: [master] : New Tests
(3)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Basic 3{color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=5959157]]
* {color:#013220}IgniteBasicWithPersistenceTestSuite:
CheckpointTest.testThrottleTargetRatioBased - PASSED{color}
* {color:#013220}IgniteBasicWithPersistenceTestSuite:
CheckpointTest.testThrottleSpeedBased - PASSED{color}
* {color:#013220}IgniteBasicWithPersistenceTestSuite:
CheckpointTest.testCheckpoint - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5959218&buildTypeId=IgniteTests24Java8_RunAll]
> Add checkpoit information to performance statistics.
>
>
> Key: IGNITE-14385
> URL: https://issues.apache.org/jira/browse/IGNITE-14385
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Sergei Ryzhov
>Assignee: Sergei Ryzhov
>Priority: Minor
> Labels: IEP-35
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Add start/end time and other parameters of checkpoint to performance
> statistics.
> Add information about throttling if necessary
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14084) Integrate direct marshalling to networking
[ https://issues.apache.org/jira/browse/IGNITE-14084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17317870#comment-17317870 ] Sergey Chugunov commented on IGNITE-14084: -- [~sdanilov], Patch looks good to me, I merged it to main branch in commit *49bfd0fc970f633615ae7e96c958650287ff7f85*. Thank you for contribution! > Integrate direct marshalling to networking > -- > > Key: IGNITE-14084 > URL: https://issues.apache.org/jira/browse/IGNITE-14084 > Project: Ignite > Issue Type: Sub-task >Reporter: Anton Kalashnikov >Assignee: Semyon Danilov >Priority: Major > Labels: iep-66, ignite-3 > Time Spent: 2h 10m > Remaining Estimate: 0h > > Direct marshalling can be extracted from ignite2.x and integrate to > ignite3.0. It helps to avoid extra data copy during the sending/receiving > messages. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14084) Integrate direct marshalling to networking
[ https://issues.apache.org/jira/browse/IGNITE-14084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-14084: -- Fix Version/s: 3.0.0-alpha2 > Integrate direct marshalling to networking > -- > > Key: IGNITE-14084 > URL: https://issues.apache.org/jira/browse/IGNITE-14084 > Project: Ignite > Issue Type: Sub-task >Reporter: Anton Kalashnikov >Assignee: Semyon Danilov >Priority: Major > Labels: iep-66, ignite-3 > Fix For: 3.0.0-alpha2 > > Time Spent: 2h 10m > Remaining Estimate: 0h > > Direct marshalling can be extracted from ignite2.x and integrate to > ignite3.0. It helps to avoid extra data copy during the sending/receiving > messages. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14460) Implement RAFT server stub
[ https://issues.apache.org/jira/browse/IGNITE-14460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-14460: -- Fix Version/s: 3.0.0-alpha2 > Implement RAFT server stub > -- > > Key: IGNITE-14460 > URL: https://issues.apache.org/jira/browse/IGNITE-14460 > Project: Ignite > Issue Type: Task >Reporter: Alexey Scherbakov >Assignee: Alexey Scherbakov >Priority: Major > Labels: iep-61, ignite-3 > Fix For: 3.0.0-alpha2 > > Time Spent: 40m > Remaining Estimate: 0h > > We need a raft server implementation stub to unlock further development of > dependent services. > In the simplest approach we will have a single node raft groups, so no > consensus is required. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13816) Add top-level dirs "config" and "logs" for .ignitecfg
[ https://issues.apache.org/jira/browse/IGNITE-13816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-13816: -- Fix Version/s: 3.0.0-alpha1 > Add top-level dirs "config" and "logs" for .ignitecfg > - > > Key: IGNITE-13816 > URL: https://issues.apache.org/jira/browse/IGNITE-13816 > Project: Ignite > Issue Type: Sub-task >Reporter: Kirill Gusakov >Assignee: Kirill Gusakov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha1 > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13751) Add javadoc validation to sanity check.
[ https://issues.apache.org/jira/browse/IGNITE-13751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-13751: -- Fix Version/s: 3.0.0-alpha2 > Add javadoc validation to sanity check. > --- > > Key: IGNITE-13751 > URL: https://issues.apache.org/jira/browse/IGNITE-13751 > Project: Ignite > Issue Type: Improvement >Reporter: Andrey Mashenkov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha2 > > > Let's add javadoc validation plugin for sanity checks and make it run on TC. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13751) Add javadoc validation to sanity check.
[ https://issues.apache.org/jira/browse/IGNITE-13751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-13751: -- Summary: Add javadoc validation to sanity check. (was: Add maven plugins to new repo.) > Add javadoc validation to sanity check. > --- > > Key: IGNITE-13751 > URL: https://issues.apache.org/jira/browse/IGNITE-13751 > Project: Ignite > Issue Type: Improvement >Reporter: Andrey Mashenkov >Priority: Major > Labels: ignite-3 > > Let's add maven plugin for sanity checks and make run on TC > * checkstyle plugin > * PMD > * licence checker > * javadoc checker > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13751) Add javadoc validation to sanity check.
[ https://issues.apache.org/jira/browse/IGNITE-13751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-13751: -- Description: Let's add javadoc validation plugin for sanity checks and make it run on TC. was: Let's add maven plugin for sanity checks and make run on TC * checkstyle plugin * PMD * licence checker * javadoc checker > Add javadoc validation to sanity check. > --- > > Key: IGNITE-13751 > URL: https://issues.apache.org/jira/browse/IGNITE-13751 > Project: Ignite > Issue Type: Improvement >Reporter: Andrey Mashenkov >Priority: Major > Labels: ignite-3 > > Let's add javadoc validation plugin for sanity checks and make it run on TC. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13751) Add javadoc validation to sanity check.
[ https://issues.apache.org/jira/browse/IGNITE-13751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-13751: -- Priority: Critical (was: Major) > Add javadoc validation to sanity check. > --- > > Key: IGNITE-13751 > URL: https://issues.apache.org/jira/browse/IGNITE-13751 > Project: Ignite > Issue Type: Improvement >Reporter: Andrey Mashenkov >Priority: Critical > Labels: ignite-3 > Fix For: 3.0.0-alpha2 > > > Let's add javadoc validation plugin for sanity checks and make it run on TC. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-13751) Add javadoc validation to sanity check.
[ https://issues.apache.org/jira/browse/IGNITE-13751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Ivanov reassigned IGNITE-13751: - Assignee: Peter Ivanov > Add javadoc validation to sanity check. > --- > > Key: IGNITE-13751 > URL: https://issues.apache.org/jira/browse/IGNITE-13751 > Project: Ignite > Issue Type: Improvement >Reporter: Andrey Mashenkov >Assignee: Peter Ivanov >Priority: Critical > Labels: ignite-3 > Fix For: 3.0.0-alpha2 > > > Let's add javadoc validation plugin for sanity checks and make it run on TC. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14346) Implement Azure Blob Storage Based IP Finder
[
https://issues.apache.org/jira/browse/IGNITE-14346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17317910#comment-17317910
]
Ilya Kasnacheev commented on IGNITE-14346:
--
I have tried the fresh build of the PR, now the dependencies issue seems
resolved, but there are at least two new issues:
If IPv6 is active, I get the following error:
{code}
class org.apache.ignite.IgniteException: URLDecoder: Illegal hex characters in
escape (%) pattern - Error at index 0 in: "lo"
at
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:1098)
at org.apache.ignite.Ignition.start(Ignition.java:356)
at
org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:367)
Caused by: class org.apache.ignite.IgniteCheckedException: URLDecoder: Illegal
hex characters in escape (%) pattern - Error at index 0 in: "lo"
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1454)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:2112)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1758)
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1143)
at
org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:1061)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:947)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:846)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:716)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:685)
at org.apache.ignite.Ignition.start(Ignition.java:353)
... 1 more
Caused by: java.lang.IllegalArgumentException: URLDecoder: Illegal hex
characters in escape (%) pattern - Error at index 0 in: "lo"
at java.base/java.net.URLDecoder.decode(URLDecoder.java:232)
at java.base/java.net.URLDecoder.decode(URLDecoder.java:142)
at com.azure.storage.common.Utility.decode(Utility.java:91)
at com.azure.storage.common.Utility.urlDecode(Utility.java:82)
at
com.azure.storage.blob.BlobContainerAsyncClient.getBlobAsyncClient(BlobContainerAsyncClient.java:144)
at
com.azure.storage.blob.BlobContainerAsyncClient.getBlobAsyncClient(BlobContainerAsyncClient.java:125)
at
com.azure.storage.blob.BlobContainerClient.getBlobClient(BlobContainerClient.java:76)
at
org.apache.ignite.spi.discovery.tcp.ipfinder.azure.TcpDiscoveryAzureBlobStoreIpFinder.registerAddresses(TcpDiscoveryAzureBlobStoreIpFinder.java:140)
at
org.apache.ignite.spi.discovery.tcp.ipfinder.TcpDiscoveryIpFinderAdapter.initializeLocalAddresses(TcpDiscoveryIpFinderAdapter.java:66)
at
org.apache.ignite.spi.discovery.tcp.TcpDiscoveryImpl.registerLocalNodeAddress(TcpDiscoveryImpl.java:401)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl.spiStart(ServerImpl.java:457)
at
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.spiStart(TcpDiscoverySpi.java:2166)
at
org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:278)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.start(GridDiscoveryManager.java:981)
at
org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1965)
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1323)
... 10 more
Failed to start grid: URLDecoder: Illegal hex characters in escape (%) pattern
- Error at index 0 in: "lo"
{code}
I believe this is because IPv6 binding addresses have %interface prepended to
them (::1%localhost, ::1%eth0), it looks like they need some extra escaping in
your use case.
When IPv6 is on, azure discovery will start all right but cluster will not
assemble - neither of my two nodes will discover itself and start. Maybe I'm
doing something wrong? My Azure container has some entries (see attach) but
cluster does not come online in a few minutes. When using static discovery, the
cluster is up and running instantly.
Please advise.
> Implement Azure Blob Storage Based IP Finder
>
>
> Key: IGNITE-14346
> URL: https://issues.apache.org/jira/browse/IGNITE-14346
> Project: Ignite
> Issue Type: Improvement
>Reporter: Atri Sharma
>Assignee: Atri Sharma
>Priority: Major
> Labels: ReviewNeeded
> Attachments: Screenshot 2021-03-23 at 8.42.31 PM.png, Screenshot
> 2021-03-23 at 8.43.31 PM.png, Screenshot 2021-03-23 at 8.44.11 PM.png,
> Screenshot 2021-03-23 at 8.45.05 PM.png
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14346) Implement Azure Blob Storage Based IP Finder
[ https://issues.apache.org/jira/browse/IGNITE-14346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kasnacheev updated IGNITE-14346: - Attachment: azure-container.png > Implement Azure Blob Storage Based IP Finder > > > Key: IGNITE-14346 > URL: https://issues.apache.org/jira/browse/IGNITE-14346 > Project: Ignite > Issue Type: Improvement >Reporter: Atri Sharma >Assignee: Atri Sharma >Priority: Major > Labels: ReviewNeeded > Attachments: Screenshot 2021-03-23 at 8.42.31 PM.png, Screenshot > 2021-03-23 at 8.43.31 PM.png, Screenshot 2021-03-23 at 8.44.11 PM.png, > Screenshot 2021-03-23 at 8.45.05 PM.png, azure-container.png > > Time Spent: 2h 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14474) Improve error message in case rebalance fails
[
https://issues.apache.org/jira/browse/IGNITE-14474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rodion updated IGNITE-14474:
Fix Version/s: 2.11
> Improve error message in case rebalance fails
> -
>
> Key: IGNITE-14474
> URL: https://issues.apache.org/jira/browse/IGNITE-14474
> Project: Ignite
> Issue Type: Improvement
>Reporter: Denis Chudov
>Assignee: Rodion
>Priority: Major
> Fix For: 2.11
>
>
> Currently we can get a message like this when rebalance fails with an
> exception (examples from ignite 2.5, in newer versions the log messages were
> changed but the problem is still actual):
> {code:java}
> 2019-11-27 13:41:14,504[WARN ][utility-#79%xxx%][GridDhtPartitionDemander]
> Rebalancing from node cancelled [grp=ignite-sys-cache,
> topVer=AffinityTopologyVersion [topVer=1932, minorTopVer=1],
> supplier=f014f30a-77f2-4459-aa5b-6c12907a7449, topic=0]. Supply message
> couldn't be unmarshalled: class o.a.i.IgniteCheckedException: Failed to
> unmarshal object with optimized marshaller
> 2019-11-27 13:41:14,504[INFO ][utility-#79%xxx%][GridDhtPartitionDemander]
> Cancelled rebalancing [grp=ignite-sys-cache,
> supplier=f014f30a-77f2-4459-aa5b-6c12907a7449, topVer=AffinityTopologyVersion
> [topVer=1932, minorTopVer=1], time=88 ms]
> 2019-11-27 13:41:14,508[WARN ][utility-#76%xxx%][GridDhtPartitionDemander]
> Rebalancing from node cancelled [grp=ignite-sys-cache,
> topVer=AffinityTopologyVersion [topVer=1932, minorTopVer=1],
> supplier=dfa5ee06-48c9-4458-ae55-48cc6ceda998, topic=0]. Supply message
> couldn't be unmarshalled: class o.a.i.IgniteCheckedException: Failed to
> unmarshal object with optimized marshaller
> {code}
> In the case above, a marshalling exception leads to rebalance failure which
> will never be resolved - i.e. the cluster enters into a erroneous state.
> We should report issues like this as ERROR. The message should explain that
> the rebalance has failed, data for the cache was not fully copied to the
> node, the backup factor is not recovered and the cluster may not work
> correctly.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14474) Improve error message in case rebalance fails
[
https://issues.apache.org/jira/browse/IGNITE-14474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rodion updated IGNITE-14474:
Fix Version/s: (was: 2.11)
> Improve error message in case rebalance fails
> -
>
> Key: IGNITE-14474
> URL: https://issues.apache.org/jira/browse/IGNITE-14474
> Project: Ignite
> Issue Type: Improvement
>Reporter: Denis Chudov
>Assignee: Rodion
>Priority: Major
>
> Currently we can get a message like this when rebalance fails with an
> exception (examples from ignite 2.5, in newer versions the log messages were
> changed but the problem is still actual):
> {code:java}
> 2019-11-27 13:41:14,504[WARN ][utility-#79%xxx%][GridDhtPartitionDemander]
> Rebalancing from node cancelled [grp=ignite-sys-cache,
> topVer=AffinityTopologyVersion [topVer=1932, minorTopVer=1],
> supplier=f014f30a-77f2-4459-aa5b-6c12907a7449, topic=0]. Supply message
> couldn't be unmarshalled: class o.a.i.IgniteCheckedException: Failed to
> unmarshal object with optimized marshaller
> 2019-11-27 13:41:14,504[INFO ][utility-#79%xxx%][GridDhtPartitionDemander]
> Cancelled rebalancing [grp=ignite-sys-cache,
> supplier=f014f30a-77f2-4459-aa5b-6c12907a7449, topVer=AffinityTopologyVersion
> [topVer=1932, minorTopVer=1], time=88 ms]
> 2019-11-27 13:41:14,508[WARN ][utility-#76%xxx%][GridDhtPartitionDemander]
> Rebalancing from node cancelled [grp=ignite-sys-cache,
> topVer=AffinityTopologyVersion [topVer=1932, minorTopVer=1],
> supplier=dfa5ee06-48c9-4458-ae55-48cc6ceda998, topic=0]. Supply message
> couldn't be unmarshalled: class o.a.i.IgniteCheckedException: Failed to
> unmarshal object with optimized marshaller
> {code}
> In the case above, a marshalling exception leads to rebalance failure which
> will never be resolved - i.e. the cluster enters into a erroneous state.
> We should report issues like this as ERROR. The message should explain that
> the rebalance has failed, data for the cache was not fully copied to the
> node, the backup factor is not recovered and the cluster may not work
> correctly.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14321) Forced index rebuilding does not work correctly
[ https://issues.apache.org/jira/browse/IGNITE-14321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Tkalenko updated IGNITE-14321: - Reviewer: Taras Ledkov (was: Yury Gerzhedovich) > Forced index rebuilding does not work correctly > --- > > Key: IGNITE-14321 > URL: https://issues.apache.org/jira/browse/IGNITE-14321 > Project: Ignite > Issue Type: Bug > Components: sql >Reporter: Kirill Tkalenko >Assignee: Kirill Tkalenko >Priority: Major > Fix For: 2.11 > > Time Spent: 3h > Remaining Estimate: 0h > > At the moment, it is not possible to force an index rebuild twice (or more) > even if the first run fails, and this also applies to command *control.sh > --cache indexes_force_rebuild*. > Thus, we need to fix: > * *GridCacheDatabaseSharedManager#forceRebuildIndexes* > * *CacheIndexesForceRebuild#execute* -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14321) Forced index rebuilding does not work correctly
[ https://issues.apache.org/jira/browse/IGNITE-14321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17317925#comment-17317925 ] Kirill Tkalenko commented on IGNITE-14321: -- [~tledkov-gridgain] Please make code review. > Forced index rebuilding does not work correctly > --- > > Key: IGNITE-14321 > URL: https://issues.apache.org/jira/browse/IGNITE-14321 > Project: Ignite > Issue Type: Bug > Components: sql >Reporter: Kirill Tkalenko >Assignee: Kirill Tkalenko >Priority: Major > Fix For: 2.11 > > Time Spent: 3h > Remaining Estimate: 0h > > At the moment, it is not possible to force an index rebuild twice (or more) > even if the first run fails, and this also applies to command *control.sh > --cache indexes_force_rebuild*. > Thus, we need to fix: > * *GridCacheDatabaseSharedManager#forceRebuildIndexes* > * *CacheIndexesForceRebuild#execute* -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14507) Un-deprecate IGNITE_BINARY_SORT_OBJECT_FIELDS
[ https://issues.apache.org/jira/browse/IGNITE-14507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17317928#comment-17317928 ] Ilya Kasnacheev commented on IGNITE-14507: -- I have merged this change. > Un-deprecate IGNITE_BINARY_SORT_OBJECT_FIELDS > - > > Key: IGNITE-14507 > URL: https://issues.apache.org/jira/browse/IGNITE-14507 > Project: Ignite > Issue Type: Improvement > Components: binary >Reporter: Stanislav Lukyanov >Assignee: Kirill Tkalenko >Priority: Major > Fix For: 2.11 > > Time Spent: 50m > Remaining Estimate: 0h > > IGNITE_BINARY_SORT_OBJECT_FIELDS should not be deprecated - on the contrary, > every new environment better have this option. We need to advertise it more, > so we need to remove the deprecation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14505) Print information about striped pool in metrics for local node
[
https://issues.apache.org/jira/browse/IGNITE-14505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17317938#comment-17317938
]
Ignite TC Bot commented on IGNITE-14505:
{panel:title=Branch: [pull/8988/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8988/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5958031&buildTypeId=IgniteTests24Java8_RunAll]
> Print information about striped pool in metrics for local node
> --
>
> Key: IGNITE-14505
> URL: https://issues.apache.org/jira/browse/IGNITE-14505
> Project: Ignite
> Issue Type: Improvement
>Reporter: Denis Mekhanikov
>Assignee: Denis Mekhanikov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently only information about public and system thread pools are printed
> in metrics for a local node. It would be good to have the same information
> about striped pool as well.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14501) Ignite 3: Fix toString implementations
[
https://issues.apache.org/jira/browse/IGNITE-14501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Mashenkov updated IGNITE-14501:
--
Labels: ignite-3 (was: )
> Ignite 3: Fix toString implementations
> --
>
> Key: IGNITE-14501
> URL: https://issues.apache.org/jira/browse/IGNITE-14501
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexey Goncharuk
>Assignee: Andrey Mashenkov
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha2
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> There is a number of places in the codebase where autogenerated IDEA
> {{toString()}} implementations are used (for example, {{ModuleRegistry}},
> {{NetworkMember}})) or non-conformant {{toString()}} implementations
> ({{Peer}} in raft-client).
> We need to fix the {{toString()}} implementations and move
> GridToStringBuilder from Ignite 2.x to avoid further similar issues.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-14511) Putting bytes to cache converted to string by default.
[
https://issues.apache.org/jira/browse/IGNITE-14511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Daschinsky reassigned IGNITE-14511:
Assignee: Ivan Daschinsky
> Putting bytes to cache converted to string by default.
> --
>
> Key: IGNITE-14511
> URL: https://issues.apache.org/jira/browse/IGNITE-14511
> Project: Ignite
> Issue Type: Bug
> Components: python, thin client
>Affects Versions: python-0.3.4
>Reporter: Ivan Daschinsky
>Assignee: Ivan Daschinsky
>Priority: Major
> Fix For: python-0.4.0
>
>
> Currently, when you put {{b'\x01\x02}} to cache without a type hint, you
> will get string {{'\x01\x02'}}. It is very confusing. If you put {{bytes}}
> with
> {{value_hint=ByteArrayObject}} you will get {{bytearray}}. As for me, it is
> quite
> strange to return mutable {{bytearray}} instead of {{bytes}}
> I suggest following:
> 1. By default treat {{bytes}} as {{ByteArrayObject}}
> 2. Method {{to_python}} of {{ByteArrayObject}} to {{bytes}}, not to
> {{bytearray}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14511) Putting bytes to cache converted to string by default.
Ivan Daschinsky created IGNITE-14511:
Summary: Putting bytes to cache converted to string by default.
Key: IGNITE-14511
URL: https://issues.apache.org/jira/browse/IGNITE-14511
Project: Ignite
Issue Type: Bug
Components: python, thin client
Affects Versions: python-0.3.4
Reporter: Ivan Daschinsky
Currently, when you put {{b'\x01\x02}} to cache without a type hint, you
will get string {{'\x01\x02'}}. It is very confusing. If you put {{bytes}} with
{{value_hint=ByteArrayObject}} you will get {{bytearray}}. As for me, it is
quite
strange to return mutable {{bytearray}} instead of {{bytes}}
I suggest following:
1. By default treat {{bytes}} as {{ByteArrayObject}}
2. Method {{to_python}} of {{ByteArrayObject}} to {{bytes}}, not to
{{bytearray}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14511) Putting bytes to cache converted to string by default.
[
https://issues.apache.org/jira/browse/IGNITE-14511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Daschinsky updated IGNITE-14511:
-
Fix Version/s: python-0.4.0
> Putting bytes to cache converted to string by default.
> --
>
> Key: IGNITE-14511
> URL: https://issues.apache.org/jira/browse/IGNITE-14511
> Project: Ignite
> Issue Type: Bug
> Components: python, thin client
>Affects Versions: python-0.3.4
>Reporter: Ivan Daschinsky
>Priority: Major
> Fix For: python-0.4.0
>
>
> Currently, when you put {{b'\x01\x02}} to cache without a type hint, you
> will get string {{'\x01\x02'}}. It is very confusing. If you put {{bytes}}
> with
> {{value_hint=ByteArrayObject}} you will get {{bytearray}}. As for me, it is
> quite
> strange to return mutable {{bytearray}} instead of {{bytes}}
> I suggest following:
> 1. By default treat {{bytes}} as {{ByteArrayObject}}
> 2. Method {{to_python}} of {{ByteArrayObject}} to {{bytes}}, not to
> {{bytearray}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14505) Print information about striped pool in metrics for local node
[ https://issues.apache.org/jira/browse/IGNITE-14505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17317996#comment-17317996 ] Denis Mekhanikov commented on IGNITE-14505: --- [~ilyak] could you take a look at the fix? > Print information about striped pool in metrics for local node > -- > > Key: IGNITE-14505 > URL: https://issues.apache.org/jira/browse/IGNITE-14505 > Project: Ignite > Issue Type: Improvement >Reporter: Denis Mekhanikov >Assignee: Denis Mekhanikov >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Currently only information about public and system thread pools are printed > in metrics for a local node. It would be good to have the same information > about striped pool as well. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13976) WAL disable/enable with node restarts results in mismatching state, data loss
[ https://issues.apache.org/jira/browse/IGNITE-13976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17318005#comment-17318005 ] Ilya Kasnacheev commented on IGNITE-13976: -- https://github.com/apache/ignite/pull/8643 LGTM now, the only red flag is misplaced cache context access in ClusterCachesInfo [~sergeychugunov] > WAL disable/enable with node restarts results in mismatching state, data loss > - > > Key: IGNITE-13976 > URL: https://issues.apache.org/jira/browse/IGNITE-13976 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.9.1 >Reporter: Ilya Kasnacheev >Assignee: Sergey Chugunov >Priority: Critical > Time Spent: 10m > Remaining Estimate: 0h > > If you try to enable/disable WAL on unstable topology, you will get to state > when WAL status is undefined, nodes might have different wall status and the > only way to fix it is to restart the cluster, which will lead to data loss > because ignite removes data if WAL is disabled on restart. > See the reproducer in PR. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14430) Common logger interface.
[ https://issues.apache.org/jira/browse/IGNITE-14430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17318044#comment-17318044 ] Alexey Scherbakov commented on IGNITE-14430: [~amashenkov] LGTM > Common logger interface. > > > Key: IGNITE-14430 > URL: https://issues.apache.org/jira/browse/IGNITE-14430 > Project: Ignite > Issue Type: Improvement >Reporter: Andrey Mashenkov >Assignee: Andrey Mashenkov >Priority: Major > Labels: ignite-3, newbie > Fix For: 3.0.0-alpha2 > > Time Spent: 10m > Remaining Estimate: 0h > > 1. Introduce a common interface for a logger, like it was done in Ignite to > abstract from any 3-rd party logger implementation. > This will give users the freedom to choose any logger in the future, and > prevent possible issues related to unwanted dependencies or dependency > versions. > 2. Add a default implementation based on System.Logger, which was introduced > in Java 9, to the core module. > 3. Remove any 3-rd party logger dependencies in all modules and switch to > IgniteLogger if possible. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13399) CpuLoad metric reports -1 under Java 11 in embedded mode
[
https://issues.apache.org/jira/browse/IGNITE-13399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17318082#comment-17318082
]
Ignite TC Bot commented on IGNITE-13399:
{panel:title=Branch: [pull/8903/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8903/head] Base: [master] : New Tests
(2)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Cache 9{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=5958096]]
* {color:#013220}IgniteCacheTestSuite9: SystemMetricsTest.testTotalSystemMemory
- PASSED{color}
* {color:#013220}IgniteCacheTestSuite9: SystemMetricsTest.testCpuLoadMetric -
PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5958134&buildTypeId=IgniteTests24Java8_RunAll]
> CpuLoad metric reports -1 under Java 11 in embedded mode
>
>
> Key: IGNITE-13399
> URL: https://issues.apache.org/jira/browse/IGNITE-13399
> Project: Ignite
> Issue Type: Bug
>Reporter: Denis Mekhanikov
>Assignee: Denis Mekhanikov
>Priority: Major
> Fix For: 2.11
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> When running a node in embedded mode under Java 11, the CpuLoad metric
> reports -1. The process needs to be started with the following option:
> {{--add-opens jdk.management/com.sun.management.internal=ALL-UNNAMED}}
> We need to get rid of this requirement to run Java with additional flags to
> get proper values for the CpuLoad metric.
> Some investigation was done under the following issue:
> https://issues.apache.org/jira/browse/IGNITE-13306
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14330) Table binary view initial implementation.
[ https://issues.apache.org/jira/browse/IGNITE-14330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17318103#comment-17318103 ] Vladislav Pyatkov commented on IGNITE-14330: I see nothing that block this patch to merge. > Table binary view initial implementation. > - > > Key: IGNITE-14330 > URL: https://issues.apache.org/jira/browse/IGNITE-14330 > Project: Ignite > Issue Type: Improvement >Reporter: Andrey Mashenkov >Assignee: Andrey Mashenkov >Priority: Major > Labels: iep-54, ignite-3 > Fix For: 3.0.0-alpha2 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > Let's implement minimal functionality from Table binary API for Ignite-3 MVP > release. > * -schema-aware ? builders for Tuples.- > * Tuple <--> Row marshaller or converter. > * basic operation (put, get, remove). > * some CAS operation (getAndPut, putIfAbsend, replace) > * add tests for these operations. > Example class is a good start point. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13019) Unexpected JOIN result when querying a single-node cluster
[
https://issues.apache.org/jira/browse/IGNITE-13019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17318122#comment-17318122
]
Maksim Timonin commented on IGNITE-13019:
-
[~slukyanov] hi! Thanks for the answer, this is correct.
I debug a code and found 2 places where I can put the check:
1. On AST parsing phase (GridSqlQuerySplitter.split0 -> splitter.splitQuery);
2. After that while building collocated model for checking distributedJoins
flag (GridSqlQuerySplitter.split0).
In my PR [1] I've decided to add a check on the AST parsing phase, due to
there are already some similar checks (hasOuterJoinReplicatedPartitioned) for
example. WDYT, is it a right direction?
[1] https://github.com/apache/ignite/pull/8744/files
> Unexpected JOIN result when querying a single-node cluster
> --
>
> Key: IGNITE-13019
> URL: https://issues.apache.org/jira/browse/IGNITE-13019
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.8
>Reporter: Stanilovsky Evgeny
>Assignee: Maksim Timonin
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Check reproducer near,
> seems something wrong with pkey logic , if we change it - results will be ok.
> {code:java}
> @Test
> public void test() throws Exception {
> inlineSize = 10;
> startGrid(0);
> String t1 = "CREATE TABLE dept\n" +
> " (\n" +
> "deptno LONG,\n" +
> "dname VARCHAR,\n" +
> "loc VARCHAR,\n" +
> "CONSTRAINT pk_dept PRIMARY KEY (deptno)\n" +
> " );";
> execSql(t1);
> String t2 = "CREATE TABLE emp\n" +
> " (\n" +
> "empno LONG,\n" +
> "ename VARCHAR,\n" +
> "job VARCHAR,\n" +
> "mgr INTEGER,\n" +
> "hiredate DATE,\n" +
> "sal LONG,\n" +
> "comm LONG,\n" +
> "deptno LONG,\n" +
> "CONSTRAINT pk_emp PRIMARY KEY (empno)\n" +
> " );";
> execSql(t2);
> execSql("insert into dept (deptno, dname, loc) values (10,
> 'ACCOUNTING', 'NEW YORK');");
> execSql("insert into dept (deptno, dname, loc) values(20, 'RESEARCH',
> 'DALLAS');");
> execSql("insert into dept (deptno, dname, loc) values(30, 'SALES',
> 'CHICAGO');");
> execSql("insert into emp (empno, ename, job, mgr, hiredate, sal,
> comm, deptno) values(7839, 'KING', 'PRESIDENT', null,
> to_date('17-11-1981','dd-mm-'), 5000, null, 10);");
> execSql("insert into emp (empno, ename, job, mgr, hiredate, sal,
> comm, deptno) values( 7698, 'BLAKE', 'MANAGER', 7839,
> to_date('1-5-1981','dd-mm-'), 2850, null, 30);");
> execSql("insert into emp (empno, ename, job, mgr, hiredate, sal,
> comm, deptno) values(7782, 'CLARK', 'MANAGER', 7839,
> to_date('9-6-1981','dd-mm-'), 2450, null, 10);");
> List> vals1 = execSql("SELECT d.deptno,\n" +
> "e.ename\n" +
> "FROM EMP e\n" +
> "INNER JOIN dept d\n" +
> "ON e.deptno = d.deptno AND e.deptno = 10;");
> assertEquals(vals1.size(), 2);
> List> vals2 = execSql("SELECT d.deptno,\n" +
> "e.ename\n" +
> "FROM EMP e\n" +
> "INNER JOIN dept d\n" +
> "ON e.deptno = d.deptno AND d.DEPTNO = 10;");
> //assertEquals(vals2.size(), 2); <--* uncomment for fail*
> execSql("drop table dept");
> String t3 = "CREATE TABLE dept\n" +
> " (\n" +
> "deptno LONG,\n" +
> "dname VARCHAR,\n" +
> "loc VARCHAR,\n" +
> "CONSTRAINT pk_dept PRIMARY KEY (deptno, dname)\n" +
> " );";
> execSql(t3);
> execSql("insert into dept (deptno, dname, loc) values (10,
> 'ACCOUNTING', 'NEW YORK');");
> execSql("insert into dept (deptno, dname, loc) values(20, 'RESEARCH',
> 'DALLAS');");
> execSql("insert into dept (deptno, dname, loc) values(30, 'SALES',
> 'CHICAGO');");
> List> vals11 = execSql("SELECT d.deptno,\n" +
> "e.ename\n" +
> "FROM EMP e\n" +
> "INNER JOIN dept d\n" +
> "ON e.deptno = d.deptno AND e.deptno = 10;");
> assertEquals(vals11.size(), 2);
> List> vals22 = execSql("SELECT d.deptno,\n" +
> "e.ename\n" +
> "FROM EMP e\n" +
> "INNER JOIN dept d\n" +
> "ON e.deptno = d.deptno AND d.DEPTNO = 10;");
> assertEquals(vals22.size(), 2);
> }
> /** */
> private List> execSql(String qry) {
> return grid(0).context().query()
> .querySqlFields(new SqlFieldsQuery(qry).setLazy(true), false)
> .getAll();
>
[jira] [Commented] (IGNITE-12920) Static hierarchy in jmx tree
[
https://issues.apache.org/jira/browse/IGNITE-12920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17318126#comment-17318126
]
Ignite TC Bot commented on IGNITE-12920:
{panel:title=Branch: [pull/8972/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8972/head] Base: [master] : New Tests
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Basic 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5959446]]
* {color:#013220}IgniteBasicTestSuite: GridMBeanSelfTest.testMbeanCreation -
PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5959321&buildTypeId=IgniteTests24Java8_RunAll]
> Static hierarchy in jmx tree
>
>
> Key: IGNITE-12920
> URL: https://issues.apache.org/jira/browse/IGNITE-12920
> Project: Ignite
> Issue Type: Improvement
>Reporter: Igor Akkuratov
>Assignee: Igor Akkuratov
>Priority: Major
> Attachments: image-2020-04-20-17-05-36-451.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Current jmx tree hierarchy depends on jvm and ignite options and contains
> classloader by default.
> !image-2020-04-20-17-05-36-451.png!
> Monitoring systems like zabbix use bean path to discover metrics. Classloader
> is been changing after node restart and monitoring systems rediscover new
> metrics. If you'll try to disable classloader with option
> {code:java}
> IGNITE_MBEAN_APPEND_CLASS_LOADER_ID=false{code}
> the jmx tree will exclude one level. This behavior excludes an opportunity to
> create single monitoring template for different deployments. It can also make
> troubles if you want to start more then one ignite instance in single jvm. In
> this case you'll have to set {color:#1d1c1d}igniteInstanceName{color}
> property to add one more level with the name of this instance. It will affect
> jmx tree hierarchy as well.
> I propose to make hierarchy unchangeable and select one of the following
> values.
> If exist instancename
> else if exist consistantId
>
> In cases with enabled persistent storage consistent id would be the same
> between node restarts, in in-memory cases you will be able to specify
> instanceName.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-14486) Implement Table binary view.
[ https://issues.apache.org/jira/browse/IGNITE-14486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov reassigned IGNITE-14486: - Assignee: (was: Andrey Mashenkov) > Implement Table binary view. > > > Key: IGNITE-14486 > URL: https://issues.apache.org/jira/browse/IGNITE-14486 > Project: Ignite > Issue Type: Improvement >Reporter: Andrey Mashenkov >Priority: Major > Labels: iep-54, ignite-3 > > Implement Table binary projection API. > Extend existed tests to all table operations (maybe excl. invoke > IGNITE-14488). > Example class is a good start point. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-14487) Implement KeyValue binary view.
[ https://issues.apache.org/jira/browse/IGNITE-14487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov reassigned IGNITE-14487: - Assignee: (was: Andrey Mashenkov) > Implement KeyValue binary view. > --- > > Key: IGNITE-14487 > URL: https://issues.apache.org/jira/browse/IGNITE-14487 > Project: Ignite > Issue Type: Improvement >Reporter: Andrey Mashenkov >Priority: Major > Labels: iep-54, ignite-3 > > Implement Table Key-value Binary projection API. > Extend existed tests to all table operations (maybe excl. invoke > IGNITE-14488). > Example class is a good start point. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-14488) Implement invoke operations for table views.
[ https://issues.apache.org/jira/browse/IGNITE-14488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov reassigned IGNITE-14488: - Assignee: (was: Andrey Mashenkov) > Implement invoke operations for table views. > > > Key: IGNITE-14488 > URL: https://issues.apache.org/jira/browse/IGNITE-14488 > Project: Ignite > Issue Type: Improvement >Reporter: Andrey Mashenkov >Priority: Major > Labels: iep-54, ignite-3 > > Implement invoke operation for all Table views (Table/KV, binary/non-binary). > * Invoke processor input depends on a view the user calls an invoke() method > on. > Thus, a view type should be a part of an atomic/tx protocol and > * InvocationContext should convert a Row to expected types on server-side. > * Any exceptions related to InvokeProc and/or it's arguments deserialization > failure or a Row deserialization failure MUST be described in the javadoc to > invoke() methods and correctly handled. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14404) Highlight that Ignite supports only Java 8 and 11
[ https://issues.apache.org/jira/browse/IGNITE-14404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17318210#comment-17318210 ] Denis A. Magda commented on IGNITE-14404: - Thanks [~igusev], merged! > Highlight that Ignite supports only Java 8 and 11 > - > > Key: IGNITE-14404 > URL: https://issues.apache.org/jira/browse/IGNITE-14404 > Project: Ignite > Issue Type: Improvement > Components: documentation >Reporter: Nikita Safonov >Assignee: Igor Gusev >Priority: Major > Labels: docuentation > Time Spent: 10m > Remaining Estimate: 0h > > We need to say that Ignite supports only Java 8 and Java 11. > The current doc implies that it supports Java 8+ > See the table here: > https://ignite.apache.org/docs/latest/quick-start/java#prerequisites -- This message was sent by Atlassian Jira (v8.3.4#803005)
