[jira] [Created] (IGNITE-925) We should correctly handle cross-cache query exceptions
Pavel Konstantinov created IGNITE-925: - Summary: We should correctly handle cross-cache query exceptions Key: IGNITE-925 URL: https://issues.apache.org/jira/browse/IGNITE-925 Project: Ignite Issue Type: Bug Components: cache Affects Versions: sprint-5 Reporter: Pavel Konstantinov Assignee: Sergi Vladykin Fix For: sprint-5 Grid with two nodes. Node1 contains cache1 with Type1 Node2 contains cache2 with Type2 Query: select * from 'cache1'.type1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-923) IgniteJclLogger.isQuiet() implementation has a bug.
[
https://issues.apache.org/jira/browse/IGNITE-923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Artem Shutak updated IGNITE-923:
Description:
The bug is based on user ticket:
http://apache-ignite-users.70518.x6.nabble.com/Disable-ignite-console-logs-td310.html#a330.
Current implementation of IgniteJclLogger.isQuiet()
{code}
@Override public boolean isQuiet() {
return !isInfoEnabled() !isDebugEnabled();
}
{code}
Current implementation of Log4JLogger.isQuiet() related to IGNITE_QUITE command
line property.
IgniteLogger.isQuiet() javadoc say:
{noformat}
/**
* Tests whether {@code info} and {@code debug} levels are turned off.
*
* @return Whether {@code info} and {@code debug} levels are turned off.
*/
{noformat}
I think Log4JLogger has right implementation and we should change javadoc and
fix IgniteJclLogger.isQuiet().
There are a workflow for user request (to disable all Ignite messages): need to
configure separate logger for org.ignite.logger in INFO (or higher) level:
For example (JCL with log4j2):
{code}
?xml version=1.0 encoding=UTF-8?
Configuration status=WARN
Appenders
Console name=Console target=SYSTEM_OUT
PatternLayout pattern=%d{HH:mm:ss.SSS} [%t] %-5level %logger{36}
- %msg%n/
/Console
/Appenders
Loggers
Logger name=org.apache.ignite level=INFO additivity=false
!--Don't log at console.--
/Logger
Root level=INFO
AppenderRef ref=Console/
/Root
/Loggers
/Configuration
{code}
was:
The bug is based on user ticket:
http://apache-ignite-users.70518.x6.nabble.com/Disable-ignite-console-logs-td310.html#a330.
Current implementation
{code}
@Override public boolean isQuiet() {
return !isInfoEnabled() !isDebugEnabled();
}
{code}
There are a workflow (to disable all Ignite messages): need to delete
appenderes for org.apache.ignite.
For example (JCL with log4j2.):
{code}
?xml version=1.0 encoding=UTF-8?
Configuration status=WARN
Appenders
Console name=Console target=SYSTEM_OUT
PatternLayout pattern=%d{HH:mm:ss.SSS} [%t] %-5level %logger{36}
- %msg%n/
/Console
/Appenders
Loggers
Logger name=org.apache.ignite level=DEBUG additivity=false
!--Don't log at console.--
/Logger
Root level=DEBUG
AppenderRef ref=Console/
/Root
/Loggers
/Configuration
{code}
IgniteJclLogger.isQuiet() implementation has a bug.
---
Key: IGNITE-923
URL: https://issues.apache.org/jira/browse/IGNITE-923
Project: Ignite
Issue Type: Bug
Reporter: Artem Shutak
Priority: Minor
The bug is based on user ticket:
http://apache-ignite-users.70518.x6.nabble.com/Disable-ignite-console-logs-td310.html#a330.
Current implementation of IgniteJclLogger.isQuiet()
{code}
@Override public boolean isQuiet() {
return !isInfoEnabled() !isDebugEnabled();
}
{code}
Current implementation of Log4JLogger.isQuiet() related to IGNITE_QUITE
command line property.
IgniteLogger.isQuiet() javadoc say:
{noformat}
/**
* Tests whether {@code info} and {@code debug} levels are turned off.
*
* @return Whether {@code info} and {@code debug} levels are turned off.
*/
{noformat}
I think Log4JLogger has right implementation and we should change javadoc and
fix IgniteJclLogger.isQuiet().
There are a workflow for user request (to disable all Ignite messages): need
to configure separate logger for org.ignite.logger in INFO (or higher)
level:
For example (JCL with log4j2):
{code}
?xml version=1.0 encoding=UTF-8?
Configuration status=WARN
Appenders
Console name=Console target=SYSTEM_OUT
PatternLayout pattern=%d{HH:mm:ss.SSS} [%t] %-5level
%logger{36} - %msg%n/
/Console
/Appenders
Loggers
Logger name=org.apache.ignite level=INFO additivity=false
!--Don't log at console.--
/Logger
Root level=INFO
AppenderRef ref=Console/
/Root
/Loggers
/Configuration
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-927) Revisit license packaging
Yakov Zhdanov created IGNITE-927: Summary: Revisit license packaging Key: IGNITE-927 URL: https://issues.apache.org/jira/browse/IGNITE-927 Project: Ignite Issue Type: Task Reporter: Yakov Zhdanov Assignee: Anton Vinogradov Priority: Blocker Fix For: sprint-5 - there's a few other licence files included but the software isn’t bundled: ./modules/ssh/licenses/jcraft-revised-bsd.txt ./modules/tools/licenses/jodd-revised-bsd.txt ./modules/visor-console/licenses/jcraft-revised-bsd.txt -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-926) Binary release should end with -bin
[ https://issues.apache.org/jira/browse/IGNITE-926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yakov Zhdanov updated IGNITE-926: - Description: * Add apache to the artefact names * Binary release should end with -bin was:Add apache to the artefact names Binary release should end with -bin - Key: IGNITE-926 URL: https://issues.apache.org/jira/browse/IGNITE-926 Project: Ignite Issue Type: Task Reporter: Anton Vinogradov Assignee: Anton Vinogradov Fix For: sprint-5 * Add apache to the artefact names * Binary release should end with -bin -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-926) Binary release should end with -bin
[ https://issues.apache.org/jira/browse/IGNITE-926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yakov Zhdanov updated IGNITE-926: - Description: Add apache to the artefact names Binary release should end with -bin - Key: IGNITE-926 URL: https://issues.apache.org/jira/browse/IGNITE-926 Project: Ignite Issue Type: Task Reporter: Anton Vinogradov Assignee: Anton Vinogradov Fix For: sprint-5 Add apache to the artefact names -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-923) IgniteLogger.isQuiet() implementations are inconsistent.
[
https://issues.apache.org/jira/browse/IGNITE-923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Artem Shutak updated IGNITE-923:
Description:
The bug is based on user ticket:
http://apache-ignite-users.70518.x6.nabble.com/Disable-ignite-console-logs-td310.html#a330.
1. IgniteLogger.isQuiet() javadoc says:
{noformat}
/**
* Tests whether {@code info} and {@code debug} levels are turned off.
*
* @return Whether {@code info} and {@code debug} levels are turned off.
*/
{noformat}
Current implementation of IgniteJclLogger.isQuiet() (accroding to javadoc).
{code}
@Override public boolean isQuiet() {
return !isInfoEnabled() !isDebugEnabled();
}
{code}
Current implementation of Log4JLogger.isQuiet() related to IGNITE_QUITE command
line property.
I think Log4JLogger has right implementation and we should change javadoc and
fix IgniteJclLogger.isQuiet().
2. There are a workflow for user request (to disable all Ignite messages): need
to configure separate logger for org.ignite.logger in INFO (or higher) level:
For example (JCL with log4j2):
{code}
?xml version=1.0 encoding=UTF-8?
Configuration status=WARN
Appenders
Console name=Console target=SYSTEM_OUT
PatternLayout pattern=%d{HH:mm:ss.SSS} [%t] %-5level %logger{36}
- %msg%n/
/Console
/Appenders
Loggers
Logger name=org.apache.ignite level=INFO additivity=false
!--Don't log at console.--
/Logger
Root level=INFO
AppenderRef ref=Console/
/Root
/Loggers
/Configuration
{code}
was:
The bug is based on user ticket:
http://apache-ignite-users.70518.x6.nabble.com/Disable-ignite-console-logs-td310.html#a330.
1. IgniteLogger.isQuiet() javadoc says:
{noformat}
/**
* Tests whether {@code info} and {@code debug} levels are turned off.
*
* @return Whether {@code info} and {@code debug} levels are turned off.
*/
{noformat}
Current implementation of IgniteJclLogger.isQuiet()
{code}
@Override public boolean isQuiet() {
return !isInfoEnabled() !isDebugEnabled();
}
{code}
Current implementation of Log4JLogger.isQuiet() related to IGNITE_QUITE command
line property.
I think Log4JLogger has right implementation and we should change javadoc and
fix IgniteJclLogger.isQuiet().
2. There are a workflow for user request (to disable all Ignite messages): need
to configure separate logger for org.ignite.logger in INFO (or higher) level:
For example (JCL with log4j2):
{code}
?xml version=1.0 encoding=UTF-8?
Configuration status=WARN
Appenders
Console name=Console target=SYSTEM_OUT
PatternLayout pattern=%d{HH:mm:ss.SSS} [%t] %-5level %logger{36}
- %msg%n/
/Console
/Appenders
Loggers
Logger name=org.apache.ignite level=INFO additivity=false
!--Don't log at console.--
/Logger
Root level=INFO
AppenderRef ref=Console/
/Root
/Loggers
/Configuration
{code}
IgniteLogger.isQuiet() implementations are inconsistent.
Key: IGNITE-923
URL: https://issues.apache.org/jira/browse/IGNITE-923
Project: Ignite
Issue Type: Bug
Reporter: Artem Shutak
Priority: Minor
The bug is based on user ticket:
http://apache-ignite-users.70518.x6.nabble.com/Disable-ignite-console-logs-td310.html#a330.
1. IgniteLogger.isQuiet() javadoc says:
{noformat}
/**
* Tests whether {@code info} and {@code debug} levels are turned off.
*
* @return Whether {@code info} and {@code debug} levels are turned off.
*/
{noformat}
Current implementation of IgniteJclLogger.isQuiet() (accroding to javadoc).
{code}
@Override public boolean isQuiet() {
return !isInfoEnabled() !isDebugEnabled();
}
{code}
Current implementation of Log4JLogger.isQuiet() related to IGNITE_QUITE
command line property.
I think Log4JLogger has right implementation and we should change javadoc and
fix IgniteJclLogger.isQuiet().
2. There are a workflow for user request (to disable all Ignite messages):
need to configure separate logger for org.ignite.logger in INFO (or higher)
level:
For example (JCL with log4j2):
{code}
?xml version=1.0 encoding=UTF-8?
Configuration status=WARN
Appenders
Console name=Console target=SYSTEM_OUT
PatternLayout pattern=%d{HH:mm:ss.SSS} [%t] %-5level
%logger{36} - %msg%n/
/Console
/Appenders
Loggers
Logger name=org.apache.ignite level=INFO additivity=false
!--Don't log at console.--
/Logger
Root level=INFO
AppenderRef ref=Console/
/Root
/Loggers
/Configuration
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-926) Binary release should end with -bin
[ https://issues.apache.org/jira/browse/IGNITE-926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yakov Zhdanov updated IGNITE-926: - Summary: Binary release should end with -bin (was: Binary release should ends with -bin) Binary release should end with -bin - Key: IGNITE-926 URL: https://issues.apache.org/jira/browse/IGNITE-926 Project: Ignite Issue Type: Task Reporter: Anton Vinogradov Assignee: Anton Vinogradov Fix For: sprint-5 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-926) Binary release should ends with -bin
[ https://issues.apache.org/jira/browse/IGNITE-926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-926: Fix Version/s: sprint-5 Binary release should ends with -bin -- Key: IGNITE-926 URL: https://issues.apache.org/jira/browse/IGNITE-926 Project: Ignite Issue Type: Task Reporter: Anton Vinogradov Assignee: Anton Vinogradov Fix For: sprint-5 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-456) [Public TC] Need to complete patch validation mechanism.
[
https://issues.apache.org/jira/browse/IGNITE-456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14552618#comment-14552618
]
tc_commenter commented on IGNITE-456:
-
Test comment
[Public TC] Need to complete patch validation mechanism.
Key: IGNITE-456
URL: https://issues.apache.org/jira/browse/IGNITE-456
Project: Ignite
Issue Type: Improvement
Components: general
Affects Versions: sprint-1
Reporter: Konstantin Boudnik
Assignee: Artem Shutak
Priority: Blocker
Fix For: sprint-5
Attachments: ignite-456-patch-validation-2.txt, patch-456-2.file,
patch-456.file
h4. Original task scope: Public TC test builds need to accept the optional
parameter
Test builds should be able to accept the following optional parameter:
- JIRA number
If the parameter is passed in, then an extra build step needs to be execute
to get the latest attachment from the JIRA ticket and {{git am}} it into the
local Ignite repo before running the tests.
Important to notice, the the patch needs to be applied once before running
all required tests. At some late point we might add the logic to only run
tests in the affected modules, but it could be a bit of a challenge.
h4. New scope of task
TODO:
- find way to run TC build with paramether from another build - Done
- configure new task to run all Ignite builds
- configure task to get all NEW patches from JIRAs and run them on TC
To check:
- comment on jira for which builds were started
- tasks for each patch started once
Current issues:
- curl does not work properly on agents
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (IGNITE-926) Revisit artifacts namings
[ https://issues.apache.org/jira/browse/IGNITE-926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov resolved IGNITE-926. - Resolution: Fixed Revisit artifacts namings - Key: IGNITE-926 URL: https://issues.apache.org/jira/browse/IGNITE-926 Project: Ignite Issue Type: Task Reporter: Anton Vinogradov Assignee: Anton Vinogradov Fix For: sprint-5 * Add apache to the artefact names * Binary release should end with -bin -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-456) [Public TC] Need to complete patch validation mechanism.
[
https://issues.apache.org/jira/browse/IGNITE-456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14552579#comment-14552579
]
Artem Shutak commented on IGNITE-456:
-
Test comment.
[Public TC] Need to complete patch validation mechanism.
Key: IGNITE-456
URL: https://issues.apache.org/jira/browse/IGNITE-456
Project: Ignite
Issue Type: Improvement
Components: general
Affects Versions: sprint-1
Reporter: Konstantin Boudnik
Assignee: Artem Shutak
Priority: Blocker
Fix For: sprint-5
Attachments: ignite-456-patch-validation-2.txt, patch-456-2.file,
patch-456.file
h4. Original task scope: Public TC test builds need to accept the optional
parameter
Test builds should be able to accept the following optional parameter:
- JIRA number
If the parameter is passed in, then an extra build step needs to be execute
to get the latest attachment from the JIRA ticket and {{git am}} it into the
local Ignite repo before running the tests.
Important to notice, the the patch needs to be applied once before running
all required tests. At some late point we might add the logic to only run
tests in the affected modules, but it could be a bit of a challenge.
h4. New scope of task
TODO:
- find way to run TC build with paramether from another build - Done
- configure new task to run all Ignite builds
- configure task to get all NEW patches from JIRAs and run them on TC
To check:
- comment on jira for which builds were started
- tasks for each patch started once
Current issues:
- curl does not work properly on agents
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (IGNITE-926) Revisit artifacts namings
[ https://issues.apache.org/jira/browse/IGNITE-926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov closed IGNITE-926. --- Revisit artifacts namings - Key: IGNITE-926 URL: https://issues.apache.org/jira/browse/IGNITE-926 Project: Ignite Issue Type: Task Reporter: Anton Vinogradov Assignee: Anton Vinogradov Fix For: sprint-5 * Add apache to the artefact names * Binary release should end with -bin -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-926) Revisit artifacts namings
[ https://issues.apache.org/jira/browse/IGNITE-926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-926: Fix Version/s: sprint-4 Revisit artifacts namings - Key: IGNITE-926 URL: https://issues.apache.org/jira/browse/IGNITE-926 Project: Ignite Issue Type: Task Reporter: Anton Vinogradov Assignee: Anton Vinogradov Fix For: sprint-4, sprint-5 * Add apache to the artefact names * Binary release should end with -bin -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-141) Need to switch IgniteOptimizedMarshaller to work over the semi-portable design
[ https://issues.apache.org/jira/browse/IGNITE-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda resolved IGNITE-141. Resolution: Done (was: Implemented) Need to switch IgniteOptimizedMarshaller to work over the semi-portable design -- Key: IGNITE-141 URL: https://issues.apache.org/jira/browse/IGNITE-141 Project: Ignite Issue Type: Bug Components: general Reporter: Dmitriy Setrakyan Assignee: Valentin Kulichenko Priority: Blocker Fix For: sprint-2 The only configuration parameter that marshaller will need is a resolver for typeIds and fieldIds. We should also switch cache entry to always store values in marshalled binary form. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-141) Need to switch IgniteOptimizedMarshaller to work over the semi-portable design
[ https://issues.apache.org/jira/browse/IGNITE-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-141: --- Affects Version/s: (was: sprint-5) Need to switch IgniteOptimizedMarshaller to work over the semi-portable design -- Key: IGNITE-141 URL: https://issues.apache.org/jira/browse/IGNITE-141 Project: Ignite Issue Type: Bug Components: general Reporter: Dmitriy Setrakyan Assignee: Valentin Kulichenko Priority: Blocker Fix For: sprint-2 The only configuration parameter that marshaller will need is a resolver for typeIds and fieldIds. We should also switch cache entry to always store values in marshalled binary form. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-928) Array out of bounds in IgniteUtils.filterReachable
[
https://issues.apache.org/jira/browse/IGNITE-928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mario Ivankovits updated IGNITE-928:
Description:
There is an Array out of bounds exception in IgniteUtils.filterReachable.
You ask for list size == 1 and then get(1) instead of get(0)
{noformat}
public static ListInetAddress filterReachable(ListInetAddress addrs) {
final int reachTimeout = 2000;
if (addrs.isEmpty())
return Collections.emptyList();
if (addrs.size() == 1) {
if (reachable(addrs.get(1), reachTimeout))
return Collections.singletonList(addrs.get(1));
return Collections.emptyList();
}
{noformat}
Regards,
Mario
was:
There is an Array out of bounds exception in IgniteUtils.filterReachable.
You ask for list size == 1 and then get(1) instead of get(0)
public static ListInetAddress filterReachable(ListInetAddress addrs) {
final int reachTimeout = 2000;
if (addrs.isEmpty())
return Collections.emptyList();
if (addrs.size() == 1) {
if (reachable(addrs.get(1), reachTimeout))
return Collections.singletonList(addrs.get(1));
return Collections.emptyList();
}
Regards,
Mario
Array out of bounds in IgniteUtils.filterReachable
--
Key: IGNITE-928
URL: https://issues.apache.org/jira/browse/IGNITE-928
Project: Ignite
Issue Type: Bug
Components: general
Environment: Ignite 1.0.5
Reporter: Mario Ivankovits
There is an Array out of bounds exception in IgniteUtils.filterReachable.
You ask for list size == 1 and then get(1) instead of get(0)
{noformat}
public static ListInetAddress filterReachable(ListInetAddress addrs) {
final int reachTimeout = 2000;
if (addrs.isEmpty())
return Collections.emptyList();
if (addrs.size() == 1) {
if (reachable(addrs.get(1), reachTimeout))
return Collections.singletonList(addrs.get(1));
return Collections.emptyList();
}
{noformat}
Regards,
Mario
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-928) Array out of bounds in IgniteUtils.filterReachable
[
https://issues.apache.org/jira/browse/IGNITE-928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mario Ivankovits updated IGNITE-928:
Description:
There is an Array out of bounds exception in IgniteUtils.filterReachable.
You ask for list size == 1 and then get(1) instead of get(0)
public static ListInetAddress filterReachable(ListInetAddress addrs) {
final int reachTimeout = 2000;
if (addrs.isEmpty())
return Collections.emptyList();
if (addrs.size() == 1) {
if (reachable(addrs.get(1), reachTimeout))
return Collections.singletonList(addrs.get(1));
return Collections.emptyList();
}
Regards,
Mario
was:
There is an Array out of bounds exception in IgniteUtils.filterReachable.
You ask for list size == 1 and then get(1) instead of get(0)
public static ListInetAddress filterReachable(ListInetAddress addrs) {
final int reachTimeout = 2000;
if (addrs.isEmpty())
return Collections.emptyList();
if (addrs.size() == 1) {
if (reachable(addrs.get(1), reachTimeout))
return Collections.singletonList(addrs.get(1));
return Collections.emptyList();
}
Regards,
Mario
Array out of bounds in IgniteUtils.filterReachable
--
Key: IGNITE-928
URL: https://issues.apache.org/jira/browse/IGNITE-928
Project: Ignite
Issue Type: Bug
Components: general
Environment: Ignite 1.0.5
Reporter: Mario Ivankovits
There is an Array out of bounds exception in IgniteUtils.filterReachable.
You ask for list size == 1 and then get(1) instead of get(0)
public static ListInetAddress filterReachable(ListInetAddress addrs) {
final int reachTimeout = 2000;
if (addrs.isEmpty())
return Collections.emptyList();
if (addrs.size() == 1) {
if (reachable(addrs.get(1), reachTimeout))
return Collections.singletonList(addrs.get(1));
return Collections.emptyList();
}
Regards,
Mario
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
