[jira] [Commented] (IGNITE-8386) SQL: Make sure PK index do not use wrapped object
[
https://issues.apache.org/jira/browse/IGNITE-8386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16618476#comment-16618476
]
Ray commented on IGNITE-8386:
-
Can we expect this ticket in 2.7?
Does this ticket break compatibility with older Ignite versions with
persistence enabled?
> SQL: Make sure PK index do not use wrapped object
> -
>
> Key: IGNITE-8386
> URL: https://issues.apache.org/jira/browse/IGNITE-8386
> Project: Ignite
> Issue Type: Task
> Components: sql
>Affects Versions: 2.4
>Reporter: Vladimir Ozerov
>Assignee: Yury Gerzhedovich
>Priority: Major
> Labels: iep-19, performance
>
> Currently PK may be built over the whole {{_KEY}} column, i.e. the whole
> binary object. This could happen in two cases:
> 1) Composite PK
> 2) Plain PK but with {{WRAP_KEY}} option.
> This is critical performance issue for two reasons:
> 1) This index is effectively useless and cannot be used in any sensible
> queries; it just wastes space and makes updates slower
> 2) Binary object typically has common header bytes what may lead to excessive
> number of comparisons during index update.
> To mitigate the problem we need to ensure that index is *never* built over
> {{_KEY}}, Instead, we must always extract target columns and build normal
> index over them.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9608) Fix buttons on start demo
[ https://issues.apache.org/jira/browse/IGNITE-9608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16618466#comment-16618466 ] Alexander Kalinin commented on IGNITE-9608: --- [~pkonstantinov]Fixed button blinking. Please test with latest udates. > Fix buttons on start demo > - > > Key: IGNITE-9608 > URL: https://issues.apache.org/jira/browse/IGNITE-9608 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Alexander Kalinin >Assignee: Pavel Konstantinov >Priority: Minor > Fix For: 2.7 > > Original Estimate: 2h > Time Spent: 2h > Remaining Estimate: 0h > > !https://snag.gy/HrOW1Y.jpg! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9510) Add vertical cursor to ignite-chart component, fix tooltip positionin.
[ https://issues.apache.org/jira/browse/IGNITE-9510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov reassigned IGNITE-9510: Assignee: Alexey Kuznetsov (was: Alexander Kalinin) > Add vertical cursor to ignite-chart component, fix tooltip positionin. > -- > > Key: IGNITE-9510 > URL: https://issues.apache.org/jira/browse/IGNITE-9510 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Alexander Kalinin >Assignee: Alexey Kuznetsov >Priority: Major > Fix For: 2.7 > > > Current version of ignite chart doesn't highlight current horizontal > selection. We should add one. > Also there are issues with tooltips positioning, that also shoud be fixed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-9510) Add vertical cursor to ignite-chart component, fix tooltip positionin.
[ https://issues.apache.org/jira/browse/IGNITE-9510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-9510. Looks good to me. Merged to master. > Add vertical cursor to ignite-chart component, fix tooltip positionin. > -- > > Key: IGNITE-9510 > URL: https://issues.apache.org/jira/browse/IGNITE-9510 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Alexander Kalinin >Assignee: Alexey Kuznetsov >Priority: Major > Fix For: 2.7 > > > Current version of ignite chart doesn't highlight current horizontal > selection. We should add one. > Also there are issues with tooltips positioning, that also shoud be fixed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9510) Add vertical cursor to ignite-chart component, fix tooltip positionin.
[ https://issues.apache.org/jira/browse/IGNITE-9510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-9510: - Component/s: wizards > Add vertical cursor to ignite-chart component, fix tooltip positionin. > -- > > Key: IGNITE-9510 > URL: https://issues.apache.org/jira/browse/IGNITE-9510 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Alexander Kalinin >Assignee: Alexander Kalinin >Priority: Major > Fix For: 2.7 > > > Current version of ignite chart doesn't highlight current horizontal > selection. We should add one. > Also there are issues with tooltips positioning, that also shoud be fixed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9510) Add vertical cursor to ignite-chart component, fix tooltip positionin.
[ https://issues.apache.org/jira/browse/IGNITE-9510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-9510: - Fix Version/s: 2.7 > Add vertical cursor to ignite-chart component, fix tooltip positionin. > -- > > Key: IGNITE-9510 > URL: https://issues.apache.org/jira/browse/IGNITE-9510 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Alexander Kalinin >Assignee: Alexander Kalinin >Priority: Major > Fix For: 2.7 > > > Current version of ignite chart doesn't highlight current horizontal > selection. We should add one. > Also there are issues with tooltips positioning, that also shoud be fixed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9511) Update styling for modal windows
[ https://issues.apache.org/jira/browse/IGNITE-9511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-9511: - Fix Version/s: 2.7 > Update styling for modal windows > > > Key: IGNITE-9511 > URL: https://issues.apache.org/jira/browse/IGNITE-9511 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Alexander Kalinin >Assignee: Alexey Kuznetsov >Priority: Major > Fix For: 2.7 > > > Currently we have two way of styles - modern (confirmation, etc) and old > styled (getting started, messages ect). > The modals have to be consistent. Let's update them with new style. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-9511) Update styling for modal windows
[ https://issues.apache.org/jira/browse/IGNITE-9511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov closed IGNITE-9511. > Update styling for modal windows > > > Key: IGNITE-9511 > URL: https://issues.apache.org/jira/browse/IGNITE-9511 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Alexander Kalinin >Assignee: Alexey Kuznetsov >Priority: Major > Fix For: 2.7 > > > Currently we have two way of styles - modern (confirmation, etc) and old > styled (getting started, messages ect). > The modals have to be consistent. Let's update them with new style. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9608) Fix buttons on start demo
[ https://issues.apache.org/jira/browse/IGNITE-9608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kalinin updated IGNITE-9608: -- Remaining Estimate: 2h Original Estimate: 2h Priority: Minor (was: Trivial) > Fix buttons on start demo > - > > Key: IGNITE-9608 > URL: https://issues.apache.org/jira/browse/IGNITE-9608 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Alexander Kalinin >Assignee: Pavel Konstantinov >Priority: Minor > Fix For: 2.7 > > Original Estimate: 2h > Remaining Estimate: 2h > > !https://snag.gy/HrOW1Y.jpg! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9609) Web console: update to AngularJS 1.7.4
[ https://issues.apache.org/jira/browse/IGNITE-9609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kalinin reassigned IGNITE-9609: - Assignee: Alexander Kalinin (was: Ilya Borisov) > Web console: update to AngularJS 1.7.4 > -- > > Key: IGNITE-9609 > URL: https://issues.apache.org/jira/browse/IGNITE-9609 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Ilya Borisov >Assignee: Alexander Kalinin >Priority: Minor > Time Spent: 16m > Remaining Estimate: 0h > > Let's update package-.json to use AngularJS 1.7.4, the 1.7.3 release > introduced some interesting new feature we might use (like extra form methods > and arbitrary event/property bindings). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9608) Fix buttons on start demo
[ https://issues.apache.org/jira/browse/IGNITE-9608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kalinin reassigned IGNITE-9608: - Assignee: Pavel Konstantinov (was: Alexander Kalinin) > Fix buttons on start demo > - > > Key: IGNITE-9608 > URL: https://issues.apache.org/jira/browse/IGNITE-9608 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Alexander Kalinin >Assignee: Pavel Konstantinov >Priority: Trivial > Fix For: 2.7 > > > !https://snag.gy/HrOW1Y.jpg! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9608) Fix buttons on start demo
[ https://issues.apache.org/jira/browse/IGNITE-9608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16618436#comment-16618436 ] Alexander Kalinin commented on IGNITE-9608: --- [~pkonstantinov] I've added consisten capilals. Please check, > Fix buttons on start demo > - > > Key: IGNITE-9608 > URL: https://issues.apache.org/jira/browse/IGNITE-9608 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Alexander Kalinin >Assignee: Alexander Kalinin >Priority: Trivial > Fix For: 2.7 > > > !https://snag.gy/HrOW1Y.jpg! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9608) Fix buttons on start demo
[ https://issues.apache.org/jira/browse/IGNITE-9608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kalinin reassigned IGNITE-9608: - Assignee: Alexander Kalinin (was: Pavel Konstantinov) Some text changes needed > Fix buttons on start demo > - > > Key: IGNITE-9608 > URL: https://issues.apache.org/jira/browse/IGNITE-9608 > Project: Ignite > Issue Type: Bug > Components: wizards >Reporter: Alexander Kalinin >Assignee: Alexander Kalinin >Priority: Trivial > Fix For: 2.7 > > > !https://snag.gy/HrOW1Y.jpg! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9623) AmbiguousMatchException Introduced by New .NET Core 2.1 String.Contains Overloads
Charles Salmon created IGNITE-9623:
--
Summary: AmbiguousMatchException Introduced by New .NET Core 2.1
String.Contains Overloads
Key: IGNITE-9623
URL: https://issues.apache.org/jira/browse/IGNITE-9623
Project: Ignite
Issue Type: Bug
Affects Versions: 2.6
Environment: .NET Core 2.1
Reporter: Charles Salmon
A couple of new String.Contains overloads were proposed
[here|https://github.com/dotnet/corefx/issues/25094], and are documented as
being included in .NET Core 2.1
[here|https://docs.microsoft.com/en-us/dotnet/api/system.string.contains?view=netcore-2.1].
The {{MethodVisitor}}, provided as part of {{Apache.Ignite.Linq}} blows up
while initializing the {{Delegates}} dictionary, as the result of this.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9623) AmbiguousMatchException Introduced by New .NET Core 2.1 String.Contains Overloads
[
https://issues.apache.org/jira/browse/IGNITE-9623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Charles Salmon updated IGNITE-9623:
---
Description:
A couple of new {{String.Contains}} overloads were proposed
[here|https://github.com/dotnet/corefx/issues/25094], and are documented as
being included in .NET Core 2.1
[here|https://docs.microsoft.com/en-us/dotnet/api/system.string.contains?view=netcore-2.1].
The {{MethodVisitor}}, provided as part of {{Apache.Ignite.Linq}} blows up
while initializing the {{Delegates}} dictionary, as the result of this.
was:
A couple of new String.Contains overloads were proposed
[here|https://github.com/dotnet/corefx/issues/25094], and are documented as
being included in .NET Core 2.1
[here|https://docs.microsoft.com/en-us/dotnet/api/system.string.contains?view=netcore-2.1].
The {{MethodVisitor}}, provided as part of {{Apache.Ignite.Linq}} blows up
while initializing the {{Delegates}} dictionary, as the result of this.
> AmbiguousMatchException Introduced by New .NET Core 2.1 String.Contains
> Overloads
> -
>
> Key: IGNITE-9623
> URL: https://issues.apache.org/jira/browse/IGNITE-9623
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.6
> Environment: .NET Core 2.1
>Reporter: Charles Salmon
>Priority: Critical
> Labels: LINQ
>
> A couple of new {{String.Contains}} overloads were proposed
> [here|https://github.com/dotnet/corefx/issues/25094], and are documented as
> being included in .NET Core 2.1
> [here|https://docs.microsoft.com/en-us/dotnet/api/system.string.contains?view=netcore-2.1].
> The {{MethodVisitor}}, provided as part of {{Apache.Ignite.Linq}} blows up
> while initializing the {{Delegates}} dictionary, as the result of this.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-9365) Force backups to different AWS availability zones using only Spring XML
[ https://issues.apache.org/jira/browse/IGNITE-9365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16618414#comment-16618414 ] Valentin Kulichenko edited comment on IGNITE-9365 at 9/18/18 2:58 AM: -- [~syssoftsol], if we consider this a configuration error, then it should be an error :) Either way, the behavior needs to be consistent and predictable - we should either throw an exception, or treat null as any other value. was (Author: vkulichenko): [~syssoftsol], if we consider this a configuration error, then it should be an error :) Either way, the behavior needs to be consistent - we should either throw an exception, or treat null as any other value. > Force backups to different AWS availability zones using only Spring XML > --- > > Key: IGNITE-9365 > URL: https://issues.apache.org/jira/browse/IGNITE-9365 > Project: Ignite > Issue Type: Improvement > Components: cache > Environment: >Reporter: David Harvey >Assignee: David Harvey >Priority: Minor > Fix For: 2.7 > > Attachments: master_947962f785_availability_zones_via_spring.patch > > Original Estimate: 168h > Remaining Estimate: 168h > > As a developer, I want to be able to force cache backups each to a different > "Availability Zone", when I'm running out-of-the-box Ignite, without > additional Jars installed. "Availability zone" is a AWS feature with > different names for the same function by other cloud providers. A single > availability zone has the characteristic that some or all of the EC2 > instances in that zone can fail together due to a single fault. You have no > control over the hosts on which the EC2 instance VMs run on in AWS, except by > controlling the availability zone . > > I could write a few lines of a custom affinityBackupFilter, and configure it > a RendezvousAffinityFunction, but then I have to get it deployed on all nodes > in the cluster, and peer class loading will not work to this. The code to > do this should just be part of Ignite. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9365) Force backups to different AWS availability zones using only Spring XML
[ https://issues.apache.org/jira/browse/IGNITE-9365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16618414#comment-16618414 ] Valentin Kulichenko commented on IGNITE-9365: - [~syssoftsol], if we consider this a configuration error, then it should be an error :) Either way, the behavior needs to be consistent - we should either throw an exception, or treat null as any other value. > Force backups to different AWS availability zones using only Spring XML > --- > > Key: IGNITE-9365 > URL: https://issues.apache.org/jira/browse/IGNITE-9365 > Project: Ignite > Issue Type: Improvement > Components: cache > Environment: >Reporter: David Harvey >Assignee: David Harvey >Priority: Minor > Fix For: 2.7 > > Attachments: master_947962f785_availability_zones_via_spring.patch > > Original Estimate: 168h > Remaining Estimate: 168h > > As a developer, I want to be able to force cache backups each to a different > "Availability Zone", when I'm running out-of-the-box Ignite, without > additional Jars installed. "Availability zone" is a AWS feature with > different names for the same function by other cloud providers. A single > availability zone has the characteristic that some or all of the EC2 > instances in that zone can fail together due to a single fault. You have no > control over the hosts on which the EC2 instance VMs run on in AWS, except by > controlling the availability zone . > > I could write a few lines of a custom affinityBackupFilter, and configure it > a RendezvousAffinityFunction, but then I have to get it deployed on all nodes > in the cluster, and peer class loading will not work to this. The code to > do this should just be part of Ignite. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7861) Web console: invalid column on Activity details modal
[ https://issues.apache.org/jira/browse/IGNITE-7861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov updated IGNITE-7861: --- Attachment: screenshot-2.png > Web console: invalid column on Activity details modal > - > > Key: IGNITE-7861 > URL: https://issues.apache.org/jira/browse/IGNITE-7861 > Project: Ignite > Issue Type: Bug >Reporter: Vasiliy Sisko >Assignee: Pavel Konstantinov >Priority: Major > Attachments: Selection_094.png, screenshot-1.png, screenshot-2.png > > > Many items do not have right description -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7861) Web console: invalid column on Activity details modal
[ https://issues.apache.org/jira/browse/IGNITE-7861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16618413#comment-16618413 ] Pavel Konstantinov commented on IGNITE-7861: I found some activities with a random URL still exists !screenshot-2.png! > Web console: invalid column on Activity details modal > - > > Key: IGNITE-7861 > URL: https://issues.apache.org/jira/browse/IGNITE-7861 > Project: Ignite > Issue Type: Bug >Reporter: Vasiliy Sisko >Assignee: Pavel Konstantinov >Priority: Major > Attachments: Selection_094.png, screenshot-1.png, screenshot-2.png > > > Many items do not have right description -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-7861) Web console: invalid column on Activity details modal
[ https://issues.apache.org/jira/browse/IGNITE-7861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov reassigned IGNITE-7861: -- Assignee: Vasiliy Sisko (was: Pavel Konstantinov) > Web console: invalid column on Activity details modal > - > > Key: IGNITE-7861 > URL: https://issues.apache.org/jira/browse/IGNITE-7861 > Project: Ignite > Issue Type: Bug >Reporter: Vasiliy Sisko >Assignee: Vasiliy Sisko >Priority: Major > Attachments: Selection_094.png, screenshot-1.png, screenshot-2.png > > > Many items do not have right description -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9365) Force backups to different AWS availability zones using only Spring XML
[ https://issues.apache.org/jira/browse/IGNITE-9365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16618388#comment-16618388 ] David Harvey commented on IGNITE-9365: -- Hi [~vkulichenko]. The null case is a configuration error, and I'm less concerned with the behavior, and will defer to you, but here is my thinking. Either the attribute was misspelled, or one or both nodes did not get the environment variable/node attribute set. If we return true when the attribute on all nodes is null, then no backups at all will be created. Returning false causes the behavior to revert to the behavior without this class if the attributes are all missing. The some nodes have a null attribute case is probably even less interesting, and I agree the second null test is unnecessary, but I erred on the side of symmetry. > Force backups to different AWS availability zones using only Spring XML > --- > > Key: IGNITE-9365 > URL: https://issues.apache.org/jira/browse/IGNITE-9365 > Project: Ignite > Issue Type: Improvement > Components: cache > Environment: >Reporter: David Harvey >Assignee: David Harvey >Priority: Minor > Fix For: 2.7 > > Attachments: master_947962f785_availability_zones_via_spring.patch > > Original Estimate: 168h > Remaining Estimate: 168h > > As a developer, I want to be able to force cache backups each to a different > "Availability Zone", when I'm running out-of-the-box Ignite, without > additional Jars installed. "Availability zone" is a AWS feature with > different names for the same function by other cloud providers. A single > availability zone has the characteristic that some or all of the EC2 > instances in that zone can fail together due to a single fault. You have no > control over the hosts on which the EC2 instance VMs run on in AWS, except by > controlling the availability zone . > > I could write a few lines of a custom affinityBackupFilter, and configure it > a RendezvousAffinityFunction, but then I have to get it deployed on all nodes > in the cluster, and peer class loading will not work to this. The code to > do this should just be part of Ignite. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9365) Force backups to different AWS availability zones using only Spring XML
[
https://issues.apache.org/jira/browse/IGNITE-9365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16618233#comment-16618233
]
Valentin Kulichenko commented on IGNITE-9365:
-
Hi [~syssoftsol]. The change looks OK to me, although I'm not sure about the
way you handle null values. I don't think there should be anything special
about them - if both are nulls, then it's a match, otherwise it's not. Said
that, I think it's better to just get attribute values from both nodes and use
{{Objects.equals}} that already takes null values into account. That would
simplify the logic and make it more intuitive in my view. Do you agree?
> Force backups to different AWS availability zones using only Spring XML
> ---
>
> Key: IGNITE-9365
> URL: https://issues.apache.org/jira/browse/IGNITE-9365
> Project: Ignite
> Issue Type: Improvement
> Components: cache
> Environment:
>Reporter: David Harvey
>Assignee: David Harvey
>Priority: Minor
> Fix For: 2.7
>
> Attachments: master_947962f785_availability_zones_via_spring.patch
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> As a developer, I want to be able to force cache backups each to a different
> "Availability Zone", when I'm running out-of-the-box Ignite, without
> additional Jars installed. "Availability zone" is a AWS feature with
> different names for the same function by other cloud providers. A single
> availability zone has the characteristic that some or all of the EC2
> instances in that zone can fail together due to a single fault. You have no
> control over the hosts on which the EC2 instance VMs run on in AWS, except by
> controlling the availability zone .
>
> I could write a few lines of a custom affinityBackupFilter, and configure it
> a RendezvousAffinityFunction, but then I have to get it deployed on all nodes
> in the cluster, and peer class loading will not work to this. The code to
> do this should just be part of Ignite.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9617) Different input possibilities for services page
[
https://issues.apache.org/jira/browse/IGNITE-9617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617845#comment-16617845
]
ASF GitHub Bot commented on IGNITE-9617:
asfgit closed pull request #11: IGNITE-9617 Different input possibilities for
services page
URL: https://github.com/apache/ignite-teamcity-bot/pull/11
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git
a/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/TcHelper.java
b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/TcHelper.java
index 02da6ca..641c9db 100644
--- a/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/TcHelper.java
+++ b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/TcHelper.java
@@ -180,6 +180,10 @@ private BranchesTracked getTrackedBranches() {
) {
try (IAnalyticsEnabledTeamcity teamcity = server(srvId, prov)) {
List builds =
teamcity.getFinishedBuildsIncludeSnDepFailed(buildTypeId, branchForTc);
+
+if (builds.isEmpty())
+return false;
+
BuildRef build = builds.get(builds.size() - 1);
String comment;
@@ -193,9 +197,8 @@ private BranchesTracked getTrackedBranches() {
return false;
}
-if ("finished".equals(build.state)) {
+if ("finished".equals(build.state))
return teamcity.sendJiraComment(ticket, comment);
-}
return false;
}
diff --git
a/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/observer/ObserverTask.java
b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/observer/ObserverTask.java
index aa3c2f5..fcc1e86 100644
---
a/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/observer/ObserverTask.java
+++
b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/observer/ObserverTask.java
@@ -48,7 +48,7 @@
try (IAnalyticsEnabledTeamcity teamcity =
helper.server(info.srvId, info.prov)) {
Build build = teamcity.getBuild(info.build.getId());
-if (!build.state.equals("finished"))
+if (!"finished".equals(build.state))
continue;
}
diff --git
a/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/web/rest/TriggerBuild.java
b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/web/rest/TriggerBuild.java
index 19077f9..e844300 100644
---
a/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/web/rest/TriggerBuild.java
+++
b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/web/rest/TriggerBuild.java
@@ -36,6 +36,7 @@
import org.apache.ignite.ci.web.CtxListener;
import org.apache.ignite.ci.web.rest.login.ServiceUnauthorizedException;
import org.apache.ignite.ci.web.model.SimpleResult;
+import org.apache.ignite.internal.util.typedef.F;
import org.jetbrains.annotations.NotNull;
import org.jetbrains.annotations.Nullable;
@@ -73,7 +74,7 @@ public SimpleResult triggerBuild(
jiraRes = observeJira(srvId, branchForTc, ticketId, helper,
teamcity, build, prov);
}
-return new SimpleResult("Tests started." + (!jiraRes.equals("") ?
"" + jiraRes : ""));
+return new SimpleResult("Tests started." + (!jiraRes.isEmpty() ?
"" + jiraRes : ""));
}
@GET
@@ -112,7 +113,7 @@ public SimpleResult commentJiraEx(@QueryParam("serverId")
@Nullable String srvId
ticketId = getTicketId(pr);
-if (ticketId.equals("")) {
+if (ticketId.isEmpty()) {
jiraRes = "JIRA ticket can't be commented - " +
"PR title \"" + pr.getTitle() + "\" should starts with
\"IGNITE-\"." +
" Please, rename PR according to the" +
@@ -124,10 +125,10 @@ public SimpleResult commentJiraEx(@QueryParam("serverId")
@Nullable String srvId
}
if (helper.notifyJira(srvId, prov, suiteId, branchForTc, "ignite-" +
ticketId))
-return new SimpleResult("JIRA commented." + (!jiraRes.equals("") ?
jiraRes : ""));
+return new SimpleResult("JIRA commented." + (!jiraRes.isEmpty() ?
jiraRes : ""));
else
// TODO Write catched exceptions to the response.
-return new SimpleResult("JIRA wasn't commented." +
(!jiraRes.equals("") ? "" + jiraRes : ""));
+return new SimpleResult("JIRA wasn't commented." +
(!jiraRes.isEmpty() ? "" + jiraRes : ""));
}
/**
@@ -149,12 +150,12 @@ private String observeJira(
Build build,
ICredentialsProv prov
) {
-if (ticketId == null || ticketId.equals("")) {
+if (F.isEmpty(ticketId)) {
[jira] [Commented] (IGNITE-9501) Exclude newly joining nodes from exchange latch
[
https://issues.apache.org/jira/browse/IGNITE-9501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617841#comment-16617841
]
Aleksey Chetaev commented on IGNITE-9501:
-
{panel:title=Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Queries 1{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=1890763]]
* GridOrderedMessageCancelSelfTest.testTaskException (last started)
{color:#d04437}Queries (Binary Objects Simple Mapper){color} [[tests 0 JVM
CRASH , Exit Code |https://ci.ignite.apache.org/viewLog.html?buildId=1890681]]
* IgniteCacheAtomicNearEnabledFieldsQuerySelfTest.testSingleResultUsesFindOne
(last started)
{color:#d04437}Data Structures{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=1890762]]
*
GridCachePartitionedDataStructuresFailoverSelfTest.testCanCloseSetInInterruptedThread
(last started)
{color:#d04437}Cache 7 (With Persistence){color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=1890765]]
* WalModeChangeAdvancedSelfTest.testServerRestartNonCoordinator (last started)
{color:#d04437}Cache 5{color} [[tests 1 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=1890761]]
* IgniteCacheTestSuite5:
IgniteCachePartitionLossPolicySelfTest.testReadWriteSafeWithBackupsAfterKillThreeNodes
- 0,0% fails in last 100 master runs.
* IgniteCacheGroupsPartitionLossPolicySelfTest.testIgnore (last started)
{color:#d04437}Cache 2{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=1890758]]
* CacheLockReleaseNodeLeaveTest.testTxLockRelease2 (last started)
{color:#d04437}ZooKeeper (Discovery) 1{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=1890720]]
* ZookeeperDiscoverySpiTest.testConcurrentStartStop1 (last started)
{color:#d04437}Binary Objects (Simple Mapper Compute Grid){color} [[tests 0
TIMEOUT , Exit Code |https://ci.ignite.apache.org/viewLog.html?buildId=1890680]]
* GridTaskFailoverAffinityRunTest.testNodeRestartClient (last started)
{color:#d04437}Compute (Grid){color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=1890685]]
* GridTaskFailoverAffinityRunTest.testNodeRestartClient (last started)
{color:#d04437}Cache 1{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=1890757]]
* GridCacheStopSelfTest.testStopMultithreaded (last started)
{color:#d04437}Activate | Deactivate Cluster{color} [[tests 0 JVM CRASH , Exit
Code |https://ci.ignite.apache.org/viewLog.html?buildId=1890679]]
* IgniteClusterActivateDeactivateTest.testDeactivateSimple_5_Servers2 (last
started)
{color:#d04437}Cache (Failover) 1{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=1890749]]
*
IgniteAtomicLongChangingTopologySelfTest.testClientCollocatedSetCreateCloseFailover
(last started)
{color:#d04437}Java Thin Client{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=1890704]]
{color:#d04437}Cache (Failover) 2{color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=1890750]]
* IgniteCacheFailoverTestSuite2:
CacheAsyncOperationsFailoverAtomicTest.testAsyncFailover - 0,0% fails in last
100 master runs.
* IgniteCacheFailoverTestSuite2:
CacheAsyncOperationsFailoverAtomicTest.testPutAllAsyncFailover - 0,0% fails in
last 100 master runs.
{color:#d04437}Cache 6{color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=1890745]]
* IgniteCacheTestSuite6:
PartitionsExchangeCoordinatorFailoverTest.testNewCoordinatorCompletedExchange -
0,0% fails in last 100 master runs.
* IgniteCacheTestSuite6:
TxRollbackAsyncNearCacheTest.testMixedAsyncRollbackTypes - 0,0% fails in last
100 master runs.
* IgniteCacheTestSuite6: TxRollbackAsyncTest.testMixedAsyncRollbackTypes - 0,0%
fails in last 100 master runs.
{color:#d04437}Cache 8{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=1890770]]
* IgniteCacheTestSuite8:
GridCacheRebalancingSyncCheckDataTest.testDataRebalancing - 0,0% fails in last
100 master runs.
{color:#d04437}Java Client{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=1890699]]
* IgniteClientTestSuite: ClientTcpDirectMultiNodeSelfTest.testTopologyListener
- 0,0% fails in last 100 master runs.
{color:#d04437}Binary Objects (Simple Mapper Basic){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=1890677]]
* IgniteBinarySimpleNameMapperBasicTestSuite:
GridDiscoveryManagerAliveCacheSelfTest.testAlives - 0,0% fails in last 100
master runs.
{color:#d04437}Basic 1{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=1890774]]
* IgniteBasicTestSuite:
DataRegionMetricsSelfTest.testAllocationRateMultiThreaded - 0,0% fails in last
100 master runs.
* IgniteBasicTestSuite:
[jira] [Commented] (IGNITE-9501) Exclude newly joining nodes from exchange latch
[
https://issues.apache.org/jira/browse/IGNITE-9501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617810#comment-16617810
]
Aleksey Chetaev commented on IGNITE-9501:
-
{panel:title=Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Queries 1{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=1890763]]
{color:#d04437}Queries (Binary Objects Simple Mapper){color} [[tests 0 JVM
CRASH , Exit Code |https://ci.ignite.apache.org/viewLog.html?buildId=1890681]]
{color:#d04437}Data Structures{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=1890762]]
*
GridCachePartitionedDataStructuresFailoverSelfTest.testCanCloseSetInInterruptedThread
(last started)
{color:#d04437}Cache 7 (With Persistence){color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=1890765]]
* WalModeChangeAdvancedSelfTest.testServerRestartNonCoordinator (last started)
{color:#d04437}Cache 5{color} [[tests 1 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=1890761]]
* IgniteCacheTestSuite5:
IgniteCachePartitionLossPolicySelfTest.testReadWriteSafeWithBackupsAfterKillThreeNodes
- 0,0% fails in last 100 master runs.
{color:#d04437}Cache 2{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=1890758]]
{color:#d04437}ZooKeeper (Discovery) 1{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=1890720]]
* ZookeeperDiscoverySpiTest.testConcurrentStartStop1 (last started)
{color:#d04437}Binary Objects (Simple Mapper Compute Grid){color} [[tests 0
TIMEOUT , Exit Code |https://ci.ignite.apache.org/viewLog.html?buildId=1890680]]
{color:#d04437}Compute (Grid){color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=1890685]]
* GridTaskFailoverAffinityRunTest.testNodeRestartClient (last started)
{color:#d04437}Cache 1{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=1890757]]
{color:#d04437}Activate | Deactivate Cluster{color} [[tests 0 JVM CRASH , Exit
Code |https://ci.ignite.apache.org/viewLog.html?buildId=1890679]]
* IgniteClusterActivateDeactivateTest.testDeactivateSimple_5_Servers2 (last
started)
{color:#d04437}Cache (Failover) 1{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=1890749]]
{color:#d04437}Java Thin Client{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=1890704]]
{color:#d04437}Cache (Failover) 2{color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=1890750]]
* IgniteCacheFailoverTestSuite2:
CacheAsyncOperationsFailoverAtomicTest.testAsyncFailover - 0,0% fails in last
100 master runs.
* IgniteCacheFailoverTestSuite2:
CacheAsyncOperationsFailoverAtomicTest.testPutAllAsyncFailover - 0,0% fails in
last 100 master runs.
{color:#d04437}Cache 6{color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=1890745]]
* IgniteCacheTestSuite6:
PartitionsExchangeCoordinatorFailoverTest.testNewCoordinatorCompletedExchange -
0,0% fails in last 100 master runs.
* IgniteCacheTestSuite6:
TxRollbackAsyncNearCacheTest.testMixedAsyncRollbackTypes - 0,0% fails in last
100 master runs.
* IgniteCacheTestSuite6: TxRollbackAsyncTest.testMixedAsyncRollbackTypes - 0,0%
fails in last 100 master runs.
{color:#d04437}Cache 8{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=1890770]]
* IgniteCacheTestSuite8:
GridCacheRebalancingSyncCheckDataTest.testDataRebalancing - 0,0% fails in last
100 master runs.
{color:#d04437}Java Client{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=1890699]]
* IgniteClientTestSuite: ClientTcpDirectMultiNodeSelfTest.testTopologyListener
- 0,0% fails in last 100 master runs.
{color:#d04437}Binary Objects (Simple Mapper Basic){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=1890677]]
* IgniteBinarySimpleNameMapperBasicTestSuite:
GridDiscoveryManagerAliveCacheSelfTest.testAlives - 0,0% fails in last 100
master runs.
{color:#d04437}Basic 1{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=1890774]]
* IgniteBasicTestSuite:
DataRegionMetricsSelfTest.testAllocationRateMultiThreaded - 0,0% fails in last
100 master runs.
* IgniteBasicTestSuite: GridNioSslSelfTest.testSimpleMessages - 0,0% fails in
last 100 master runs.
{color:#d04437}Cache (Restarts) 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=1890754]]
* IgniteCacheRestartTestSuite:
IgniteCacheCreateRestartSelfTest.testStopOriginatingNode - 0,0% fails in last
100 master runs.
{color:#d04437}PDS 1{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=1890736]]
* IgnitePdsTestSuite:
IgnitePdsDestroyCacheWithoutCheckpointsTest.testDestroyCachesAbruptlyWithoutCheckpoints
- 0,0%
[jira] [Updated] (IGNITE-9622) MVCC Cache API: prohibit non PESSIMISTIC REPEATABLE_READ transactions
[ https://issues.apache.org/jira/browse/IGNITE-9622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Pavlukhin updated IGNITE-9622: --- Fix Version/s: 2.7 > MVCC Cache API: prohibit non PESSIMISTIC REPEATABLE_READ transactions > - > > Key: IGNITE-9622 > URL: https://issues.apache.org/jira/browse/IGNITE-9622 > Project: Ignite > Issue Type: Bug > Components: mvcc >Reporter: Ivan Pavlukhin >Priority: Major > Fix For: 2.7 > > > For cache with enabled mvcc we should allow running only PESSIMISTIC > REPEATABLE_READ transactions. For other modes exception should be thrown > (like is done for SQL API). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9622) MVCC Cache API: prohibit non PESSIMISTIC REPEATABLE_READ transactions
Ivan Pavlukhin created IGNITE-9622: -- Summary: MVCC Cache API: prohibit non PESSIMISTIC REPEATABLE_READ transactions Key: IGNITE-9622 URL: https://issues.apache.org/jira/browse/IGNITE-9622 Project: Ignite Issue Type: Bug Components: mvcc Reporter: Ivan Pavlukhin For cache with enabled mvcc we should allow running only PESSIMISTIC REPEATABLE_READ transactions. For other modes exception should be thrown (like is done for SQL API). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9560) Security permissions to restrict arbitrary code exectution
[ https://issues.apache.org/jira/browse/IGNITE-9560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Garus updated IGNITE-9560: Description: SecurityPermission class should be extended to cover all cases able to cause arbitrary code execution. 1) Restriction on listener registration - IgniteEvents listener - CQ listener 2) Restriction on closure (able to be executed on the remote node) execution - Compute API (seems to be covered, should be rechecked) - Services - Entry processor 3) We have to make sure that cases listed at #1 and #2 are the all possible cases. was: SecurityPermission class should be extended to cover all cases able to cause arbitrary code execution. 1) Restriction on listener registration - EventStorageSpi listener - CQ listener 2) Restriction on closure (able to be executed on the remote node) execution - Compute API (seems to be covered, should be rechecked) - Services - Entry processor 3) We have to make sure that cases listed at #1 and #2 are the all possible cases. > Security permissions to restrict arbitrary code exectution > -- > > Key: IGNITE-9560 > URL: https://issues.apache.org/jira/browse/IGNITE-9560 > Project: Ignite > Issue Type: Task > Components: security >Affects Versions: 2.6 >Reporter: Anton Vinogradov >Priority: Major > > SecurityPermission class should be extended to cover all cases able to cause > arbitrary code execution. > 1) Restriction on listener registration > - IgniteEvents listener > - CQ listener > 2) Restriction on closure (able to be executed on the remote node) execution > - Compute API (seems to be covered, should be rechecked) > - Services > - Entry processor > 3) We have to make sure that cases listed at #1 and #2 are the all possible > cases. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9621) MVCC: sqlline warning that transactions are not supported
[
https://issues.apache.org/jira/browse/IGNITE-9621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-9621:
Fix Version/s: 2.7
> MVCC: sqlline warning that transactions are not supported
> -
>
> Key: IGNITE-9621
> URL: https://issues.apache.org/jira/browse/IGNITE-9621
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Stepan Pilschikov
>Priority: Major
> Fix For: 2.7
>
>
> MVCC enabled
> --autoCommit=true
> In sqlline first initial lines throwing warning message:
> {code}
> [1;34missuing: !connect jdbc:ignite:thin://127.0.0.1:10800 '' ''
> org.apache.ignite.IgniteJdbcThinDriver[m
> [1;34mConnecting to jdbc:ignite:thin://127.0.0.1:10800[m
> [1;34mConnected to: Apache Ignite (version 2.7.1#19700101-sha1:)[m
> [1;34mDriver: Apache Ignite Thin JDBC Driver (version
> 2.7.1#19700101-sha1:)[m
> [1;34mAutocommit status: false[m
> Sep 17, 2018 5:44:32 PM
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection
> setTransactionIsolation
> WARNING: Transactions are not supported.
> Sep 17, 2018 5:44:32 PM
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection
> getTransactionIsolation
> WARNING: Transactions are not supported.
> [1;34mTransaction isolation: TRANSACTION_REPEATABLE_READ[m
> sqlline version 1.3.0
> 0: jdbc:ignite:thin://127.0.0.1:10800>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9621) MVCC: sqlline warning that transactions are not supported
[
https://issues.apache.org/jira/browse/IGNITE-9621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-9621:
Affects Version/s: (was: 2.7)
> MVCC: sqlline warning that transactions are not supported
> -
>
> Key: IGNITE-9621
> URL: https://issues.apache.org/jira/browse/IGNITE-9621
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Stepan Pilschikov
>Priority: Major
> Fix For: 2.7
>
>
> MVCC enabled
> --autoCommit=true
> In sqlline first initial lines throwing warning message:
> {code}
> [1;34missuing: !connect jdbc:ignite:thin://127.0.0.1:10800 '' ''
> org.apache.ignite.IgniteJdbcThinDriver[m
> [1;34mConnecting to jdbc:ignite:thin://127.0.0.1:10800[m
> [1;34mConnected to: Apache Ignite (version 2.7.1#19700101-sha1:)[m
> [1;34mDriver: Apache Ignite Thin JDBC Driver (version
> 2.7.1#19700101-sha1:)[m
> [1;34mAutocommit status: false[m
> Sep 17, 2018 5:44:32 PM
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection
> setTransactionIsolation
> WARNING: Transactions are not supported.
> Sep 17, 2018 5:44:32 PM
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection
> getTransactionIsolation
> WARNING: Transactions are not supported.
> [1;34mTransaction isolation: TRANSACTION_REPEATABLE_READ[m
> sqlline version 1.3.0
> 0: jdbc:ignite:thin://127.0.0.1:10800>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9620) MVCC: select throwing `Transaction is already completed` exception after mvcc missmatch
[
https://issues.apache.org/jira/browse/IGNITE-9620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-9620:
Affects Version/s: (was: 2.7)
> MVCC: select throwing `Transaction is already completed` exception after
> mvcc missmatch
>
>
> Key: IGNITE-9620
> URL: https://issues.apache.org/jira/browse/IGNITE-9620
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Stepan Pilschikov
>Priority: Major
> Fix For: 2.7
>
>
> Using sqlline with autoCommit=true
> {code}
> switch to first user
> - select * from test:
> result: [[1, 1, test_1]]
> switch to second user
> - insert into test(id, field_int, field_var) values (2, 2, 'test_2'):
> - commit:
> - select * from test:
> result: [[1, 1, test_1], [2, 2, test_2]]
> switch to first user
> - insert into test(id, field_int, field_var) values (2, 2, 'test_2'):
> error: Mvcc version mismatch.
> - select * from test
> {code}
> During last select throwing exception
> {code}
> 0: jdbc:ignite:thin://127.0.0.1:10800> select * from test;
> select * from test;
> [1;31mError: Transaction is already completed. (state=25000,code=0)[m
> java.sql.SQLException: Transaction is already completed.
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:764)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
> at sqlline.Commands.execute(Commands.java:823)
> at sqlline.Commands.sql(Commands.java:733)
> at sqlline.SqlLine.dispatch(SqlLine.java:795)
> at sqlline.SqlLine.begin(SqlLine.java:668)
> at sqlline.SqlLine.start(SqlLine.java:373)
> at sqlline.SqlLine.main(SqlLine.java:265)
> {code}
> Exception in node logs:
> {code}
> [17:44:36,234][SEVERE][jdbc-request-handler-worker-#61][JdbcRequestHandler]
> Failed to execute SQL query [reqId=0, req=JdbcQueryExecuteRequest
> [schemaName=PUBLIC, pageSize=1024, maxRows=0, sqlQry=select * from test,
> args=Object[] [], stmtType=ANY_STATEMENT_TYPE, autoCommit=false]]
> class org.apache.ignite.internal.processors.query.IgniteSQLException:
> Transaction is already completed.
> at
> org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.checkActive(MvccUtils.java:623)
> at
> org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.requestSnapshot(MvccUtils.java:780)
> at
> org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.mvccTracker(MvccUtils.java:761)
> at
> org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.mvccTracker(MvccUtils.java:744)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.runQueryTwoStep(IgniteH2Indexing.java:1731)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.doRunDistributedQuery(IgniteH2Indexing.java:2521)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.querySqlFields(IgniteH2Indexing.java:2074)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2139)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2134)
> at
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2711)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2148)
> at
> org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.executeQuery(JdbcRequestHandler.java:511)
> at
> org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.doHandle(JdbcRequestHandler.java:245)
> at
> org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandlerWorker.body(JdbcRequestHandlerWorker.java:90)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> Works for any query which is throwing mvcc missmatch exception
> After commit select query works again
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9620) MVCC: select throwing `Transaction is already completed` exception after mvcc missmatch
[
https://issues.apache.org/jira/browse/IGNITE-9620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-9620:
Fix Version/s: 2.7
> MVCC: select throwing `Transaction is already completed` exception after
> mvcc missmatch
>
>
> Key: IGNITE-9620
> URL: https://issues.apache.org/jira/browse/IGNITE-9620
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Reporter: Stepan Pilschikov
>Priority: Major
> Fix For: 2.7
>
>
> Using sqlline with autoCommit=true
> {code}
> switch to first user
> - select * from test:
> result: [[1, 1, test_1]]
> switch to second user
> - insert into test(id, field_int, field_var) values (2, 2, 'test_2'):
> - commit:
> - select * from test:
> result: [[1, 1, test_1], [2, 2, test_2]]
> switch to first user
> - insert into test(id, field_int, field_var) values (2, 2, 'test_2'):
> error: Mvcc version mismatch.
> - select * from test
> {code}
> During last select throwing exception
> {code}
> 0: jdbc:ignite:thin://127.0.0.1:10800> select * from test;
> select * from test;
> [1;31mError: Transaction is already completed. (state=25000,code=0)[m
> java.sql.SQLException: Transaction is already completed.
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:764)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
> at
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
> at sqlline.Commands.execute(Commands.java:823)
> at sqlline.Commands.sql(Commands.java:733)
> at sqlline.SqlLine.dispatch(SqlLine.java:795)
> at sqlline.SqlLine.begin(SqlLine.java:668)
> at sqlline.SqlLine.start(SqlLine.java:373)
> at sqlline.SqlLine.main(SqlLine.java:265)
> {code}
> Exception in node logs:
> {code}
> [17:44:36,234][SEVERE][jdbc-request-handler-worker-#61][JdbcRequestHandler]
> Failed to execute SQL query [reqId=0, req=JdbcQueryExecuteRequest
> [schemaName=PUBLIC, pageSize=1024, maxRows=0, sqlQry=select * from test,
> args=Object[] [], stmtType=ANY_STATEMENT_TYPE, autoCommit=false]]
> class org.apache.ignite.internal.processors.query.IgniteSQLException:
> Transaction is already completed.
> at
> org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.checkActive(MvccUtils.java:623)
> at
> org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.requestSnapshot(MvccUtils.java:780)
> at
> org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.mvccTracker(MvccUtils.java:761)
> at
> org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.mvccTracker(MvccUtils.java:744)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.runQueryTwoStep(IgniteH2Indexing.java:1731)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.doRunDistributedQuery(IgniteH2Indexing.java:2521)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.querySqlFields(IgniteH2Indexing.java:2074)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2139)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2134)
> at
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2711)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2148)
> at
> org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.executeQuery(JdbcRequestHandler.java:511)
> at
> org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.doHandle(JdbcRequestHandler.java:245)
> at
> org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandlerWorker.body(JdbcRequestHandlerWorker.java:90)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> Works for any query which is throwing mvcc missmatch exception
> After commit select query works again
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-5553) Ignite PDS 2: IgnitePersistentStoreDataStructuresTest testSet assertion error
[ https://issues.apache.org/jira/browse/IGNITE-5553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov resolved IGNITE-5553. -- Resolution: Fixed Merged to master. Thanks for the contribution. > Ignite PDS 2: IgnitePersistentStoreDataStructuresTest testSet assertion error > - > > Key: IGNITE-5553 > URL: https://issues.apache.org/jira/browse/IGNITE-5553 > Project: Ignite > Issue Type: Bug > Components: data structures, persistence >Affects Versions: 2.1 >Reporter: Dmitriy Pavlov >Assignee: Pavel Pereslegin >Priority: Major > Labels: MakeTeamcityGreenAgain, Muted_test, test-fail > Fix For: 2.7 > > > h2. Notes-4435 > When IgniteSet is restored from persistence, size of set is always 0, [link > to test > history|http://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=-7043871603266099589=testDetails]. > h2. Detailed description > Unlike *IgniteQueue* which uses separate cache key to store its size > *IgniteSet* stores it in a field of some class. > Test from the link above shows very clearly that after restoring memory state > from PDS all set values are restored correctly but size is lost. > h2. Proposed solution > One possible solution might be to do the same thing as *IgniteQueue* does: > size of *IgniteSet* must be stored is cache instead of volatile in-memory > fields of random classes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9621) MVCC: sqlline warning that transactions are not supported
[
https://issues.apache.org/jira/browse/IGNITE-9621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stepan Pilschikov updated IGNITE-9621:
--
Description:
MVCC enabled
--autoCommit=true
In sqlline first initial lines throwing warning message:
{code}
[1;34missuing: !connect jdbc:ignite:thin://127.0.0.1:10800 '' ''
org.apache.ignite.IgniteJdbcThinDriver[m
[1;34mConnecting to jdbc:ignite:thin://127.0.0.1:10800[m
[1;34mConnected to: Apache Ignite (version 2.7.1#19700101-sha1:)[m
[1;34mDriver: Apache Ignite Thin JDBC Driver (version
2.7.1#19700101-sha1:)[m
[1;34mAutocommit status: false[m
Sep 17, 2018 5:44:32 PM org.apache.ignite.internal.jdbc.thin.JdbcThinConnection
setTransactionIsolation
WARNING: Transactions are not supported.
Sep 17, 2018 5:44:32 PM org.apache.ignite.internal.jdbc.thin.JdbcThinConnection
getTransactionIsolation
WARNING: Transactions are not supported.
[1;34mTransaction isolation: TRANSACTION_REPEATABLE_READ[m
sqlline version 1.3.0
0: jdbc:ignite:thin://127.0.0.1:10800>
{code}
was:
MVCC enabled
--autoCommit=true
In sqlline first initial lines throwing warning message:
```
[1;34missuing: !connect jdbc:ignite:thin://127.0.0.1:10800 '' ''
org.apache.ignite.IgniteJdbcThinDriver[m
[1;34mConnecting to jdbc:ignite:thin://127.0.0.1:10800[m
[1;34mConnected to: Apache Ignite (version 2.7.1#19700101-sha1:)[m
[1;34mDriver: Apache Ignite Thin JDBC Driver (version
2.7.1#19700101-sha1:)[m
[1;34mAutocommit status: false[m
Sep 17, 2018 5:44:32 PM org.apache.ignite.internal.jdbc.thin.JdbcThinConnection
setTransactionIsolation
WARNING: Transactions are not supported.
Sep 17, 2018 5:44:32 PM org.apache.ignite.internal.jdbc.thin.JdbcThinConnection
getTransactionIsolation
WARNING: Transactions are not supported.
[1;34mTransaction isolation: TRANSACTION_REPEATABLE_READ[m
sqlline version 1.3.0
0: jdbc:ignite:thin://127.0.0.1:10800>
```
> MVCC: sqlline warning that transactions are not supported
> -
>
> Key: IGNITE-9621
> URL: https://issues.apache.org/jira/browse/IGNITE-9621
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
>Affects Versions: 2.7
>Reporter: Stepan Pilschikov
>Priority: Major
>
> MVCC enabled
> --autoCommit=true
> In sqlline first initial lines throwing warning message:
> {code}
> [1;34missuing: !connect jdbc:ignite:thin://127.0.0.1:10800 '' ''
> org.apache.ignite.IgniteJdbcThinDriver[m
> [1;34mConnecting to jdbc:ignite:thin://127.0.0.1:10800[m
> [1;34mConnected to: Apache Ignite (version 2.7.1#19700101-sha1:)[m
> [1;34mDriver: Apache Ignite Thin JDBC Driver (version
> 2.7.1#19700101-sha1:)[m
> [1;34mAutocommit status: false[m
> Sep 17, 2018 5:44:32 PM
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection
> setTransactionIsolation
> WARNING: Transactions are not supported.
> Sep 17, 2018 5:44:32 PM
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection
> getTransactionIsolation
> WARNING: Transactions are not supported.
> [1;34mTransaction isolation: TRANSACTION_REPEATABLE_READ[m
> sqlline version 1.3.0
> 0: jdbc:ignite:thin://127.0.0.1:10800>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9621) MVCC: sqlline warning that transactions are not supported
Stepan Pilschikov created IGNITE-9621: - Summary: MVCC: sqlline warning that transactions are not supported Key: IGNITE-9621 URL: https://issues.apache.org/jira/browse/IGNITE-9621 Project: Ignite Issue Type: Bug Components: mvcc Affects Versions: 2.7 Reporter: Stepan Pilschikov MVCC enabled --autoCommit=true In sqlline first initial lines throwing warning message: ``` [1;34missuing: !connect jdbc:ignite:thin://127.0.0.1:10800 '' '' org.apache.ignite.IgniteJdbcThinDriver[m [1;34mConnecting to jdbc:ignite:thin://127.0.0.1:10800[m [1;34mConnected to: Apache Ignite (version 2.7.1#19700101-sha1:)[m [1;34mDriver: Apache Ignite Thin JDBC Driver (version 2.7.1#19700101-sha1:)[m [1;34mAutocommit status: false[m Sep 17, 2018 5:44:32 PM org.apache.ignite.internal.jdbc.thin.JdbcThinConnection setTransactionIsolation WARNING: Transactions are not supported. Sep 17, 2018 5:44:32 PM org.apache.ignite.internal.jdbc.thin.JdbcThinConnection getTransactionIsolation WARNING: Transactions are not supported. [1;34mTransaction isolation: TRANSACTION_REPEATABLE_READ[m sqlline version 1.3.0 0: jdbc:ignite:thin://127.0.0.1:10800> ``` -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9620) MVCC: select throwing `Transaction is already completed` exception after mvcc missmatch
[
https://issues.apache.org/jira/browse/IGNITE-9620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stepan Pilschikov updated IGNITE-9620:
--
Description:
Using sqlline with autoCommit=true
{code}
switch to first user
- select * from test:
result: [[1, 1, test_1]]
switch to second user
- insert into test(id, field_int, field_var) values (2, 2, 'test_2'):
- commit:
- select * from test:
result: [[1, 1, test_1], [2, 2, test_2]]
switch to first user
- insert into test(id, field_int, field_var) values (2, 2, 'test_2'):
error: Mvcc version mismatch.
- select * from test
{code}
During last select throwing exception
{code}
0: jdbc:ignite:thin://127.0.0.1:10800> select * from test;
select * from test;
[1;31mError: Transaction is already completed. (state=25000,code=0)[m
java.sql.SQLException: Transaction is already completed.
at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:764)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
at sqlline.Commands.execute(Commands.java:823)
at sqlline.Commands.sql(Commands.java:733)
at sqlline.SqlLine.dispatch(SqlLine.java:795)
at sqlline.SqlLine.begin(SqlLine.java:668)
at sqlline.SqlLine.start(SqlLine.java:373)
at sqlline.SqlLine.main(SqlLine.java:265)
{code}
Exception in node logs:
{code}
[17:44:36,234][SEVERE][jdbc-request-handler-worker-#61][JdbcRequestHandler]
Failed to execute SQL query [reqId=0, req=JdbcQueryExecuteRequest
[schemaName=PUBLIC, pageSize=1024, maxRows=0, sqlQry=select * from test,
args=Object[] [], stmtType=ANY_STATEMENT_TYPE, autoCommit=false]]
class org.apache.ignite.internal.processors.query.IgniteSQLException:
Transaction is already completed.
at
org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.checkActive(MvccUtils.java:623)
at
org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.requestSnapshot(MvccUtils.java:780)
at
org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.mvccTracker(MvccUtils.java:761)
at
org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.mvccTracker(MvccUtils.java:744)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.runQueryTwoStep(IgniteH2Indexing.java:1731)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.doRunDistributedQuery(IgniteH2Indexing.java:2521)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.querySqlFields(IgniteH2Indexing.java:2074)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2139)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2134)
at
org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2711)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2148)
at
org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.executeQuery(JdbcRequestHandler.java:511)
at
org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.doHandle(JdbcRequestHandler.java:245)
at
org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandlerWorker.body(JdbcRequestHandlerWorker.java:90)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:748)
{code}
Works for any query which is throwing mvcc missmatch exception
After commit select query works again
was:
Using sqlline with autoCommit=false
{code}
switch to first user
- select * from test:
result: [[1, 1, test_1]]
switch to second user
- insert into test(id, field_int, field_var) values (2, 2, 'test_2'):
- commit:
- select * from test:
result: [[1, 1, test_1], [2, 2, test_2]]
switch to first user
- insert into test(id, field_int, field_var) values (2, 2, 'test_2'):
error: Mvcc version mismatch.
- select * from test
{code}
During last select throwing exception
{code}
0: jdbc:ignite:thin://127.0.0.1:10800> select * from test;
select * from test;
[1;31mError: Transaction is already completed. (state=25000,code=0)[m
java.sql.SQLException: Transaction is already completed.
at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:764)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
at sqlline.Commands.execute(Commands.java:823)
[jira] [Commented] (IGNITE-9541) Add the comparison for two general statistics "RunAll" for master in the date interval
[
https://issues.apache.org/jira/browse/IGNITE-9541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617644#comment-16617644
]
ASF GitHub Bot commented on IGNITE-9541:
SomeFire commented on a change in pull request #9: IGNITE-9541 Add the
comparison for two general statistics "RunAll" for master in the date interval
URL: https://github.com/apache/ignite-teamcity-bot/pull/9#discussion_r218096888
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/IgniteTeamcityHelper.java
##
@@ -378,7 +402,16 @@ public Build getBuild(String href) {
}
public ProblemOccurrences getProblems(Build build) {
-return getJaxbUsingHref(build.problemOccurrences.href,
ProblemOccurrences.class);
+if (build.problemOccurrences != null) {
+ProblemOccurrences problemOccurrences =
getJaxbUsingHref(build.problemOccurrences.href, ProblemOccurrences.class);
+
+problemOccurrences.problemOccurrences
+.forEach(p -> p.buildRef = build);
Review comment:
No need new line here.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Add the comparison for two general statistics "RunAll" for master in the date
> interval
> --
>
> Key: IGNITE-9541
> URL: https://issues.apache.org/jira/browse/IGNITE-9541
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Major
>
> Based on IGNITE-9333 add the comparison for two general statistics "RunAll"
> for master in the date interval
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9541) Add the comparison for two general statistics "RunAll" for master in the date interval
[
https://issues.apache.org/jira/browse/IGNITE-9541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617664#comment-16617664
]
ASF GitHub Bot commented on IGNITE-9541:
SomeFire commented on a change in pull request #9: IGNITE-9541 Add the
comparison for two general statistics "RunAll" for master in the date interval
URL: https://github.com/apache/ignite-teamcity-bot/pull/9#discussion_r218103132
##
File path: ignite-tc-helper-web/src/main/webapp/statistics.html
##
@@ -0,0 +1,213 @@
+
+
+Ignite Teamcity - statistics master's branch
+
+https://code.jquery.com/ui/1.12.1/themes/base/jquery-ui.css;>
+
+
+https://code.jquery.com/jquery-1.12.4.js";>
+https://code.jquery.com/ui/1.12.1/jquery-ui.js";>
+
+
+
+table {
+width: 70%;
+border-collapse: collapse;
+}
+td, th {
+
+padding: 10px 5px 10px 5px;
+}
+th {
+text-align: left;
+padding: 5px;
+background-color: #f5f5ff;
+color: #00;
+}
+tr:nth-child(odd) { background-color: #fafaff; }
+
+
+
[jira] [Commented] (IGNITE-9541) Add the comparison for two general statistics "RunAll" for master in the date interval
[ https://issues.apache.org/jira/browse/IGNITE-9541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617671#comment-16617671 ] ASF GitHub Bot commented on IGNITE-9541: SomeFire commented on a change in pull request #9: IGNITE-9541 Add the comparison for two general statistics "RunAll" for master in the date interval URL: https://github.com/apache/ignite-teamcity-bot/pull/9#discussion_r218102484 ## File path: ignite-tc-helper-web/src/main/webapp/statistics.html ## @@ -0,0 +1,213 @@ + + +Ignite Teamcity - statistics master's branch + +https://code.jquery.com/ui/1.12.1/themes/base/jquery-ui.css;> + + +https://code.jquery.com/jquery-1.12.4.js";> +https://code.jquery.com/ui/1.12.1/jquery-ui.js";> + + +
[jira] [Commented] (IGNITE-9541) Add the comparison for two general statistics "RunAll" for master in the date interval
[
https://issues.apache.org/jira/browse/IGNITE-9541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617663#comment-16617663
]
ASF GitHub Bot commented on IGNITE-9541:
SomeFire commented on a change in pull request #9: IGNITE-9541 Add the
comparison for two general statistics "RunAll" for master in the date interval
URL: https://github.com/apache/ignite-teamcity-bot/pull/9#discussion_r218099007
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/tcmodel/result/issues/IssueRef.java
##
@@ -0,0 +1,38 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.ignite.ci.tcmodel.result.issues;
+
+import javax.xml.bind.annotation.XmlAttribute;
+
+/**
+ * Issue short version from list of build's related issues.
+ *
+ * See example of XML, e.g. here
+ * https://ci.ignite.apache.org/app/rest/latest/builds/id:1694977/relatedIssues
+ */
+public class IssueRef {
+@XmlAttribute public String id;
+@XmlAttribute public String url;
+
+@Override public String toString() {
Review comment:
Missed javadoc.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Add the comparison for two general statistics "RunAll" for master in the date
> interval
> --
>
> Key: IGNITE-9541
> URL: https://issues.apache.org/jira/browse/IGNITE-9541
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Major
>
> Based on IGNITE-9333 add the comparison for two general statistics "RunAll"
> for master in the date interval
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9541) Add the comparison for two general statistics "RunAll" for master in the date interval
[
https://issues.apache.org/jira/browse/IGNITE-9541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617668#comment-16617668
]
ASF GitHub Bot commented on IGNITE-9541:
SomeFire commented on a change in pull request #9: IGNITE-9541 Add the
comparison for two general statistics "RunAll" for master in the date interval
URL: https://github.com/apache/ignite-teamcity-bot/pull/9#discussion_r218102850
##
File path: ignite-tc-helper-web/src/main/webapp/statistics.html
##
@@ -0,0 +1,213 @@
+
+
+Ignite Teamcity - statistics master's branch
+
+https://code.jquery.com/ui/1.12.1/themes/base/jquery-ui.css;>
+
+
+https://code.jquery.com/jquery-1.12.4.js";>
+https://code.jquery.com/ui/1.12.1/jquery-ui.js";>
+
+
+
+table {
+width: 70%;
+border-collapse: collapse;
+}
+td, th {
+
+padding: 10px 5px 10px 5px;
+}
+th {
+text-align: left;
+padding: 5px;
+background-color: #f5f5ff;
+color: #00;
+}
+tr:nth-child(odd) { background-color: #fafaff; }
+
+
+
[jira] [Commented] (IGNITE-9541) Add the comparison for two general statistics "RunAll" for master in the date interval
[ https://issues.apache.org/jira/browse/IGNITE-9541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617657#comment-16617657 ] ASF GitHub Bot commented on IGNITE-9541: SomeFire commented on a change in pull request #9: IGNITE-9541 Add the comparison for two general statistics "RunAll" for master in the date interval URL: https://github.com/apache/ignite-teamcity-bot/pull/9#discussion_r218101483 ## File path: ignite-tc-helper-web/src/main/webapp/comparison.html ## @@ -0,0 +1,286 @@ + + + + +Ignite Teamcity - comparison master's branch in the date interval + +https://code.jquery.com/ui/1.12.1/themes/base/jquery-ui.css;> + +https://cdn.jsdelivr.net/jquery/latest/jquery.min.js";> +https://cdn.jsdelivr.net/momentjs/latest/moment.min.js";> +https://cdn.jsdelivr.net/npm/daterangepicker/daterangepicker.min.js";> +https://cdn.jsdelivr.net/npm/daterangepicker/daterangepicker.css; /> + +https://d3js.org/d3.v4.min.js";> + + + + + + +DATE INTERVAL + + + +TESTS +COUNT + + + +PASSED + + + +FAILED + + + +IGNORED + + + +MUTED + + +PROBLEMS +TOTAL + + + + + + +EXECUTION_TIMEOUT + + + +JVM_CRASH + + + +OOME + + + +EXIT_CODE + + + +FAILED_TESTS + + + +SNAPSHOT_DEPENDENCY_ERROR + + + +OTHER + + + + +log1 +log2 + + + +
[jira] [Commented] (IGNITE-9541) Add the comparison for two general statistics "RunAll" for master in the date interval
[
https://issues.apache.org/jira/browse/IGNITE-9541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617669#comment-16617669
]
ASF GitHub Bot commented on IGNITE-9541:
SomeFire commented on a change in pull request #9: IGNITE-9541 Add the
comparison for two general statistics "RunAll" for master in the date interval
URL: https://github.com/apache/ignite-teamcity-bot/pull/9#discussion_r218104124
##
File path: ignite-tc-helper-web/src/main/webapp/statistics.html
##
@@ -0,0 +1,213 @@
+
+
+Ignite Teamcity - statistics master's branch
+
+https://code.jquery.com/ui/1.12.1/themes/base/jquery-ui.css;>
+
+
+https://code.jquery.com/jquery-1.12.4.js";>
+https://code.jquery.com/ui/1.12.1/jquery-ui.js";>
+
+
+
+table {
+width: 70%;
+border-collapse: collapse;
+}
+td, th {
+
+padding: 10px 5px 10px 5px;
+}
+th {
+text-align: left;
+padding: 5px;
+background-color: #f5f5ff;
+color: #00;
+}
+tr:nth-child(odd) { background-color: #fafaff; }
+
+
+
[jira] [Commented] (IGNITE-9541) Add the comparison for two general statistics "RunAll" for master in the date interval
[
https://issues.apache.org/jira/browse/IGNITE-9541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617655#comment-16617655
]
ASF GitHub Bot commented on IGNITE-9541:
SomeFire commented on a change in pull request #9: IGNITE-9541 Add the
comparison for two general statistics "RunAll" for master in the date interval
URL: https://github.com/apache/ignite-teamcity-bot/pull/9#discussion_r218104050
##
File path: ignite-tc-helper-web/src/main/webapp/statistics.html
##
@@ -0,0 +1,213 @@
+
+
+Ignite Teamcity - statistics master's branch
+
+https://code.jquery.com/ui/1.12.1/themes/base/jquery-ui.css;>
+
+
+https://code.jquery.com/jquery-1.12.4.js";>
+https://code.jquery.com/ui/1.12.1/jquery-ui.js";>
+
+
+
+table {
+width: 70%;
+border-collapse: collapse;
+}
+td, th {
+
+padding: 10px 5px 10px 5px;
+}
+th {
+text-align: left;
+padding: 5px;
+background-color: #f5f5ff;
+color: #00;
+}
+tr:nth-child(odd) { background-color: #fafaff; }
+
+
+
+
+var g_shownDataHashCodeHex = ""
+var g_updTimer = null;
+
+$(document).ready(function() {
+$.getScript("js/testfails-2.0.js", function(data, textStatus, jqxhr){
});
+
+$( document ).tooltip();
+loadData();
+//todo fix setInterval( function() { checkForUpdate(); }, 3);
+
+$.ajax({ url: "rest/branches/version", success: showVersionInfo,
error: showErrInLoadStatus });
+
+if(g_updTimer==null) {
+g_updTimer=setTimeout(tstTimeout, 3200);
+}
+setInterval(tstTimeout, 1);
+});
+
+function tstTimeout() {
+
+if(g_updTimer!=null) {
+clearTimeout(g_updTimer);
+g_updTimer=null;
+}
+
+
+var d = new Date();
+var n = d.getTime();
+
+// $(document.body).prepend("timeout at "+n+"
");
+
+
+if(g_updTimer==null) {
+g_updTimer=setTimeout(tstTimeout, 3200);
+}
+}
+
+function parmsForRest() {
+var curReqParms = "";
+var server = findGetParameter("server");
+if(server!=null) {
+curReqParms += "&server=" + server;
+}
+
+var buildType = findGetParameter("buildType");
+if(buildType!=null) {
+curReqParms += "&buildType=" + buildType;
+}
+
+var branch = findGetParameter("branch");
+if(branch!=null) {
+curReqParms += "&branch=" + branch;
+}
+
+var count = findGetParameter("count");
+if(count!=null) {
+curReqParms += "&count=" + count;
+}
+
+var sinceDate = findGetParameter("sinceDate");
+if(sinceDate!=null) {
+curReqParms += "&sinceDate=" + sinceDate;
+}
+
+var untilDate = findGetParameter("untilDate");
+if(untilDate!=null) {
+curReqParms += "&untilDate=" + untilDate;
+}
+
+curReqParms = curReqParms.replace("&","?");
+
+return curReqParms;
+}
+
+function loadData() {
+var curFailuresUrl = "rest/build/history" + parmsForRest();
+
+$("#loadStatus").html("![](<a rel="nofollow" href="https://www.wallies.com/filebin/images/loading_apple.gif">https://www.wallies.com/filebin/images/loading_apple.gif</a>)
Please wait");
+$.ajax({
+url: curFailuresUrl,
+success: function(result) {
+if(result.updateRequired ||
(isDefinedAndFilled(result.runningUpdates) && result.runningUpdates>0)) {
+setTimeout(checkForUpdate, 3000)
+$("#loadStatus").html(" Updating");
+} else {
+$("#loadStatus").html("");
+}
+showData(result);
+g_shownDataHashCodeHex =
isDefinedAndFilled(result.hashCodeHex) ? result.hashCodeHex : "";
+},
+error: showErrInLoadStatus
+});
+}
+function showData(result) {
+$("#statistics").html(showBuildHistory(result));
+}
+
+function median(arr){
+arr = arr.sort(function(a, b){ return a - b; });
+var i = arr.length / 2;
+return i % 1 == 0 ? (arr[i - 1] + arr[i]) / 2 : arr[Math.floor(i)];
+}
+
+function formatString(string) {
+if (string.indexOf("_") < string.indexOf(":"))
+string = string.substring(string.indexOf("_") + 1);
+
+return "" + string.substring(0, string.indexOf(":") + 1) + "" +
string.substring(string.indexOf(":") + 1);
+}
+
+function
[jira] [Commented] (IGNITE-9541) Add the comparison for two general statistics "RunAll" for master in the date interval
[
https://issues.apache.org/jira/browse/IGNITE-9541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617645#comment-16617645
]
ASF GitHub Bot commented on IGNITE-9541:
SomeFire commented on a change in pull request #9: IGNITE-9541 Add the
comparison for two general statistics "RunAll" for master in the date interval
URL: https://github.com/apache/ignite-teamcity-bot/pull/9#discussion_r218096565
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/IgniteTeamcityHelper.java
##
@@ -354,18 +357,39 @@ public String basicAuthToken() {
private List getBuildHistory(@Nullable String buildTypeId,
@Nullable String branchName,
boolean dfltFilter,
-@Nullable String state) {
+@Nullable String state){
+
+return getBuildHistory(buildTypeId, branchName, dfltFilter, state,
null, null);
+}
+
+private List getBuildHistory(@Nullable String buildTypeId,
+@Nullable String branchName,
+boolean dfltFilter,
+@Nullable String state,
+@Nullable Date sinceDate,
+@Nullable Date untilDate) {
String btFilter = isNullOrEmpty(buildTypeId) ? "" : ",buildType:" +
buildTypeId + "";
String stateFilter = isNullOrEmpty(state) ? "" : (",state:" + state);
-String brachFilter = isNullOrEmpty(branchName) ? "" :",branch:" +
branchName;
+String branchFilter = isNullOrEmpty(branchName) ? "" :",branch:" +
branchName;
+String sinceDateFilter = sinceDate == null ? "" : ",sinceDate:" +
getDateYyyyMmDdTHhMmSsZ(sinceDate);
+String untilDateFilter = untilDate == null ? "" : ",untilDate:" +
getDateYyyyMmDdTHhMmSsZ(untilDate);
return sendGetXmlParseJaxb(host + "app/rest/latest/builds"
+ "?locator="
+ "defaultFilter:" + dfltFilter
+ btFilter
+ stateFilter
-+ brachFilter
-+ ",count:1000", Builds.class).getBuildsNonNull();
++ branchFilter
++ ",count:" + DEFAULT_BUILDS_COUNT
++ sinceDateFilter
++ untilDateFilter, Builds.class).getBuildsNonNull();
+}
+
+public String getDateYyyyMmDdTHhMmSsZ(Date date){
+
Review comment:
Redundant blank line.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Add the comparison for two general statistics "RunAll" for master in the date
> interval
> --
>
> Key: IGNITE-9541
> URL: https://issues.apache.org/jira/browse/IGNITE-9541
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Major
>
> Based on IGNITE-9333 add the comparison for two general statistics "RunAll"
> for master in the date interval
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9541) Add the comparison for two general statistics "RunAll" for master in the date interval
[
https://issues.apache.org/jira/browse/IGNITE-9541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617660#comment-16617660
]
ASF GitHub Bot commented on IGNITE-9541:
SomeFire commented on a change in pull request #9: IGNITE-9541 Add the
comparison for two general statistics "RunAll" for master in the date interval
URL: https://github.com/apache/ignite-teamcity-bot/pull/9#discussion_r218100744
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/web/model/current/BuildStatisticsSummary.java
##
@@ -0,0 +1,293 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.ignite.ci.web.model.current;
+
+import java.text.DateFormat;
+import java.text.ParseException;
+import java.text.SimpleDateFormat;
+import java.util.ArrayList;
+import java.util.Date;
+import java.util.HashMap;
+import java.util.List;
+import java.util.Map;
+import java.util.Objects;
+import java.util.stream.Collectors;
+import java.util.stream.Stream;
+import javax.annotation.Nonnull;
+import org.apache.ignite.ci.ITeamcity;
+import org.apache.ignite.ci.tcmodel.hist.BuildRef;
+import org.apache.ignite.ci.tcmodel.result.Build;
+import org.apache.ignite.ci.tcmodel.result.TestOccurrencesRef;
+import org.apache.ignite.ci.tcmodel.result.issues.IssueRef;
+import org.apache.ignite.ci.tcmodel.result.issues.IssueUsage;
+import org.apache.ignite.ci.tcmodel.result.problems.ProblemOccurrence;
+import org.apache.ignite.ci.util.TimeUtil;
+import org.apache.ignite.ci.web.IBackgroundUpdatable;
+
+/**
+ * Summary of build statistics.
+ */
+public class BuildStatisticsSummary extends UpdateInfo implements
IBackgroundUpdatable {
+/** Short problem names. */
+public static final String TOTAL = "TOTAL";
+
+private static Map shortProblemNames = new HashMap<>();
+
+static {
+shortProblemNames.put(TOTAL, "TT");
+shortProblemNames.put(ProblemOccurrence.TC_EXECUTION_TIMEOUT, "ET");
+shortProblemNames.put(ProblemOccurrence.TC_JVM_CRASH, "JC");
+shortProblemNames.put(ProblemOccurrence.TC_OOME, "OO");
+shortProblemNames.put(ProblemOccurrence.TC_EXIT_CODE, "EC");
+shortProblemNames.put(ProblemOccurrence.TC_FAILED_TESTS, "FT");
+shortProblemNames.put(ProblemOccurrence.SNAPSHOT_DEPENDENCY_ERROR,
"SD");
+shortProblemNames.put(ProblemOccurrence.OTHER, "OT");
+}
+
+/** Build with test and problems references. */
+public Integer buildId;
+
+public String date;
+
+/** Test occurrences. */
+public TestOccurrencesRef testOccurrences;
+
+/** List of problem occurrences. */
+private List problemOccurrenceList;
+
+/** Snapshot-dependencies build run result. */
+public Map> dependenciesProblems;
+
+/** List of related issues. */
+private List relatedIssues;
+
+/** Duration printable. */
+public String durationPrintable;
+
+/** Short build run result (without snapshot-dependencies printable
result). */
+public Map totalProblems;
+
+/** Build problems count. */
+public long problemsCount;
+
+/** Is fake stub. */
+public boolean isFakeStub;
+
+/**
+ * @param buildId Build id.
+ */
+public BuildStatisticsSummary(Integer buildId){
+this.buildId = buildId;
+}
+
+/** Initialize build statistics. */
+public void initialize(@Nonnull final ITeamcity teamcity) {
+Build build = teamcity.getBuild(buildId);
+
+DateFormat dateFormat = new SimpleDateFormat("dd-MM-'T'HH:mm:ss");
+dateFormat.format(build.getFinishDate());
+date = dateFormat.format(build.getFinishDate());
+
+isFakeStub = build.isFakeStub();
+
+if (isFakeStub)
+return;
+
+testOccurrences = build.testOccurrences;
+
+relatedIssues =
teamcity.getIssuesUsagesList(build.relatedIssuesRef.href).getIssuesUsagesNonNull().stream()
+.map(IssueUsage::getIssue).collect(Collectors.toList());
+
+durationPrintable = TimeUtil
+.getDurationPrintable(build.getFinishDate().getTime() -
build.getStartDate().getTime());
+
+List snapshotDependencies =
[jira] [Commented] (IGNITE-9541) Add the comparison for two general statistics "RunAll" for master in the date interval
[
https://issues.apache.org/jira/browse/IGNITE-9541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617661#comment-16617661
]
ASF GitHub Bot commented on IGNITE-9541:
SomeFire commented on a change in pull request #9: IGNITE-9541 Add the
comparison for two general statistics "RunAll" for master in the date interval
URL: https://github.com/apache/ignite-teamcity-bot/pull/9#discussion_r218091080
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/ITeamcity.java
##
@@ -80,7 +97,11 @@
CompletableFuture> getQueuedBuilds(@Nullable String branch);
default int[] getBuildNumbersFromHistory(String projectId, String
branchNameForHist) {
-return getFinishedBuilds(projectId,
branchNameForHist).stream().mapToInt(BuildRef::getId).toArray();
+return getBuildNumbersFromHistory(projectId, branchNameForHist, null,
null);
+}
+
+default int[] getBuildNumbersFromHistory(String projectId, String
branchNameForHist, Date sinceDate, Date untilDate) {
Review comment:
Missec javadoc.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Add the comparison for two general statistics "RunAll" for master in the date
> interval
> --
>
> Key: IGNITE-9541
> URL: https://issues.apache.org/jira/browse/IGNITE-9541
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Major
>
> Based on IGNITE-9333 add the comparison for two general statistics "RunAll"
> for master in the date interval
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9541) Add the comparison for two general statistics "RunAll" for master in the date interval
[
https://issues.apache.org/jira/browse/IGNITE-9541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617658#comment-16617658
]
ASF GitHub Bot commented on IGNITE-9541:
SomeFire commented on a change in pull request #9: IGNITE-9541 Add the
comparison for two general statistics "RunAll" for master in the date interval
URL: https://github.com/apache/ignite-teamcity-bot/pull/9#discussion_r218100654
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/web/model/current/BuildStatisticsSummary.java
##
@@ -0,0 +1,293 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.ignite.ci.web.model.current;
+
+import java.text.DateFormat;
+import java.text.ParseException;
+import java.text.SimpleDateFormat;
+import java.util.ArrayList;
+import java.util.Date;
+import java.util.HashMap;
+import java.util.List;
+import java.util.Map;
+import java.util.Objects;
+import java.util.stream.Collectors;
+import java.util.stream.Stream;
+import javax.annotation.Nonnull;
+import org.apache.ignite.ci.ITeamcity;
+import org.apache.ignite.ci.tcmodel.hist.BuildRef;
+import org.apache.ignite.ci.tcmodel.result.Build;
+import org.apache.ignite.ci.tcmodel.result.TestOccurrencesRef;
+import org.apache.ignite.ci.tcmodel.result.issues.IssueRef;
+import org.apache.ignite.ci.tcmodel.result.issues.IssueUsage;
+import org.apache.ignite.ci.tcmodel.result.problems.ProblemOccurrence;
+import org.apache.ignite.ci.util.TimeUtil;
+import org.apache.ignite.ci.web.IBackgroundUpdatable;
+
+/**
+ * Summary of build statistics.
+ */
+public class BuildStatisticsSummary extends UpdateInfo implements
IBackgroundUpdatable {
+/** Short problem names. */
+public static final String TOTAL = "TOTAL";
+
+private static Map shortProblemNames = new HashMap<>();
+
+static {
+shortProblemNames.put(TOTAL, "TT");
+shortProblemNames.put(ProblemOccurrence.TC_EXECUTION_TIMEOUT, "ET");
+shortProblemNames.put(ProblemOccurrence.TC_JVM_CRASH, "JC");
+shortProblemNames.put(ProblemOccurrence.TC_OOME, "OO");
+shortProblemNames.put(ProblemOccurrence.TC_EXIT_CODE, "EC");
+shortProblemNames.put(ProblemOccurrence.TC_FAILED_TESTS, "FT");
+shortProblemNames.put(ProblemOccurrence.SNAPSHOT_DEPENDENCY_ERROR,
"SD");
+shortProblemNames.put(ProblemOccurrence.OTHER, "OT");
+}
+
+/** Build with test and problems references. */
+public Integer buildId;
+
+public String date;
+
+/** Test occurrences. */
+public TestOccurrencesRef testOccurrences;
+
+/** List of problem occurrences. */
+private List problemOccurrenceList;
+
+/** Snapshot-dependencies build run result. */
+public Map> dependenciesProblems;
+
+/** List of related issues. */
+private List relatedIssues;
+
+/** Duration printable. */
+public String durationPrintable;
+
+/** Short build run result (without snapshot-dependencies printable
result). */
+public Map totalProblems;
+
+/** Build problems count. */
+public long problemsCount;
+
+/** Is fake stub. */
+public boolean isFakeStub;
+
+/**
+ * @param buildId Build id.
+ */
+public BuildStatisticsSummary(Integer buildId){
+this.buildId = buildId;
+}
+
+/** Initialize build statistics. */
+public void initialize(@Nonnull final ITeamcity teamcity) {
+Build build = teamcity.getBuild(buildId);
+
+DateFormat dateFormat = new SimpleDateFormat("dd-MM-'T'HH:mm:ss");
+dateFormat.format(build.getFinishDate());
+date = dateFormat.format(build.getFinishDate());
+
+isFakeStub = build.isFakeStub();
+
+if (isFakeStub)
+return;
+
+testOccurrences = build.testOccurrences;
+
+relatedIssues =
teamcity.getIssuesUsagesList(build.relatedIssuesRef.href).getIssuesUsagesNonNull().stream()
+.map(IssueUsage::getIssue).collect(Collectors.toList());
+
+durationPrintable = TimeUtil
+.getDurationPrintable(build.getFinishDate().getTime() -
build.getStartDate().getTime());
+
+List snapshotDependencies =
[jira] [Commented] (IGNITE-9541) Add the comparison for two general statistics "RunAll" for master in the date interval
[
https://issues.apache.org/jira/browse/IGNITE-9541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617662#comment-16617662
]
ASF GitHub Bot commented on IGNITE-9541:
SomeFire commented on a change in pull request #9: IGNITE-9541 Add the
comparison for two general statistics "RunAll" for master in the date interval
URL: https://github.com/apache/ignite-teamcity-bot/pull/9#discussion_r218099774
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/web/model/current/BuildStatisticsSummary.java
##
@@ -0,0 +1,293 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.ignite.ci.web.model.current;
+
+import java.text.DateFormat;
+import java.text.ParseException;
+import java.text.SimpleDateFormat;
+import java.util.ArrayList;
+import java.util.Date;
+import java.util.HashMap;
+import java.util.List;
+import java.util.Map;
+import java.util.Objects;
+import java.util.stream.Collectors;
+import java.util.stream.Stream;
+import javax.annotation.Nonnull;
+import org.apache.ignite.ci.ITeamcity;
+import org.apache.ignite.ci.tcmodel.hist.BuildRef;
+import org.apache.ignite.ci.tcmodel.result.Build;
+import org.apache.ignite.ci.tcmodel.result.TestOccurrencesRef;
+import org.apache.ignite.ci.tcmodel.result.issues.IssueRef;
+import org.apache.ignite.ci.tcmodel.result.issues.IssueUsage;
+import org.apache.ignite.ci.tcmodel.result.problems.ProblemOccurrence;
+import org.apache.ignite.ci.util.TimeUtil;
+import org.apache.ignite.ci.web.IBackgroundUpdatable;
+
+/**
+ * Summary of build statistics.
+ */
+public class BuildStatisticsSummary extends UpdateInfo implements
IBackgroundUpdatable {
+/** Short problem names. */
+public static final String TOTAL = "TOTAL";
+
+private static Map shortProblemNames = new HashMap<>();
+
+static {
+shortProblemNames.put(TOTAL, "TT");
+shortProblemNames.put(ProblemOccurrence.TC_EXECUTION_TIMEOUT, "ET");
+shortProblemNames.put(ProblemOccurrence.TC_JVM_CRASH, "JC");
+shortProblemNames.put(ProblemOccurrence.TC_OOME, "OO");
+shortProblemNames.put(ProblemOccurrence.TC_EXIT_CODE, "EC");
+shortProblemNames.put(ProblemOccurrence.TC_FAILED_TESTS, "FT");
+shortProblemNames.put(ProblemOccurrence.SNAPSHOT_DEPENDENCY_ERROR,
"SD");
+shortProblemNames.put(ProblemOccurrence.OTHER, "OT");
+}
+
+/** Build with test and problems references. */
+public Integer buildId;
+
+public String date;
+
+/** Test occurrences. */
+public TestOccurrencesRef testOccurrences;
+
+/** List of problem occurrences. */
+private List problemOccurrenceList;
+
+/** Snapshot-dependencies build run result. */
+public Map> dependenciesProblems;
+
+/** List of related issues. */
+private List relatedIssues;
+
+/** Duration printable. */
+public String durationPrintable;
+
+/** Short build run result (without snapshot-dependencies printable
result). */
+public Map totalProblems;
+
+/** Build problems count. */
+public long problemsCount;
+
+/** Is fake stub. */
+public boolean isFakeStub;
+
+/**
+ * @param buildId Build id.
+ */
+public BuildStatisticsSummary(Integer buildId){
+this.buildId = buildId;
+}
+
+/** Initialize build statistics. */
+public void initialize(@Nonnull final ITeamcity teamcity) {
+Build build = teamcity.getBuild(buildId);
+
+DateFormat dateFormat = new SimpleDateFormat("dd-MM-'T'HH:mm:ss");
+dateFormat.format(build.getFinishDate());
+date = dateFormat.format(build.getFinishDate());
+
+isFakeStub = build.isFakeStub();
+
+if (isFakeStub)
+return;
+
+testOccurrences = build.testOccurrences;
+
+relatedIssues =
teamcity.getIssuesUsagesList(build.relatedIssuesRef.href).getIssuesUsagesNonNull().stream()
+.map(IssueUsage::getIssue).collect(Collectors.toList());
+
+durationPrintable = TimeUtil
+.getDurationPrintable(build.getFinishDate().getTime() -
build.getStartDate().getTime());
+
+List snapshotDependencies =
[jira] [Updated] (IGNITE-9620) MVCC: select throwing `Transaction is already completed` exception after mvcc missmatch
[
https://issues.apache.org/jira/browse/IGNITE-9620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stepan Pilschikov updated IGNITE-9620:
--
Description:
Using sqlline with autoCommit=false
{code}
switch to first user
- select * from test:
result: [[1, 1, test_1]]
switch to second user
- insert into test(id, field_int, field_var) values (2, 2, 'test_2'):
- commit:
- select * from test:
result: [[1, 1, test_1], [2, 2, test_2]]
switch to first user
- insert into test(id, field_int, field_var) values (2, 2, 'test_2'):
error: Mvcc version mismatch.
- select * from test
{code}
During last select throwing exception
{code}
0: jdbc:ignite:thin://127.0.0.1:10800> select * from test;
select * from test;
[1;31mError: Transaction is already completed. (state=25000,code=0)[m
java.sql.SQLException: Transaction is already completed.
at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:764)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
at sqlline.Commands.execute(Commands.java:823)
at sqlline.Commands.sql(Commands.java:733)
at sqlline.SqlLine.dispatch(SqlLine.java:795)
at sqlline.SqlLine.begin(SqlLine.java:668)
at sqlline.SqlLine.start(SqlLine.java:373)
at sqlline.SqlLine.main(SqlLine.java:265)
{code}
Exception in node logs:
{code}
[17:44:36,234][SEVERE][jdbc-request-handler-worker-#61][JdbcRequestHandler]
Failed to execute SQL query [reqId=0, req=JdbcQueryExecuteRequest
[schemaName=PUBLIC, pageSize=1024, maxRows=0, sqlQry=select * from test,
args=Object[] [], stmtType=ANY_STATEMENT_TYPE, autoCommit=false]]
class org.apache.ignite.internal.processors.query.IgniteSQLException:
Transaction is already completed.
at
org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.checkActive(MvccUtils.java:623)
at
org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.requestSnapshot(MvccUtils.java:780)
at
org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.mvccTracker(MvccUtils.java:761)
at
org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.mvccTracker(MvccUtils.java:744)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.runQueryTwoStep(IgniteH2Indexing.java:1731)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.doRunDistributedQuery(IgniteH2Indexing.java:2521)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.querySqlFields(IgniteH2Indexing.java:2074)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2139)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2134)
at
org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2711)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2148)
at
org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.executeQuery(JdbcRequestHandler.java:511)
at
org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.doHandle(JdbcRequestHandler.java:245)
at
org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandlerWorker.body(JdbcRequestHandlerWorker.java:90)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:748)
{code}
Works for any query which is throwing mvcc missmatch exception
After commit select query works again
was:
Using sqlline with autoCommit=false
{code}
switch to first user
- select * from test:
result: [[1, 1, test_1]]
switch to second user
- insert into test(id, field_int, field_var) values (2, 2, 'test_2'):
- commit:
- select * from test:
result: [[1, 1, test_1], [2, 2, test_2]]
switch to first user
- insert into test(id, field_int, field_var) values (2, 2, 'test_2'):
error: Mvcc version mismatch.
- select * from test
{code}
During last select throwing exception
{code}
0: jdbc:ignite:thin://127.0.0.1:10800> select * from test;
select * from test;
[1;31mError: Transaction is already completed. (state=25000,code=0)[m
java.sql.SQLException: Transaction is already completed.
at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:764)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
at sqlline.Commands.execute(Commands.java:823)
[jira] [Created] (IGNITE-9620) MVCC: select throwing `Transaction is already completed` exception after mvcc missmatch
Stepan Pilschikov created IGNITE-9620:
-
Summary: MVCC: select throwing `Transaction is already completed`
exception after mvcc missmatch
Key: IGNITE-9620
URL: https://issues.apache.org/jira/browse/IGNITE-9620
Project: Ignite
Issue Type: Bug
Components: mvcc
Affects Versions: 2.7
Reporter: Stepan Pilschikov
Using sqlline with autoCommit=false
{code}
switch to first user
- select * from test:
result: [[1, 1, test_1]]
switch to second user
- insert into test(id, field_int, field_var) values (2, 2, 'test_2'):
- commit:
- select * from test:
result: [[1, 1, test_1], [2, 2, test_2]]
switch to first user
- insert into test(id, field_int, field_var) values (2, 2, 'test_2'):
error: Mvcc version mismatch.
- select * from test
{code}
During last select throwing exception
{code}
0: jdbc:ignite:thin://127.0.0.1:10800> select * from test;
select * from test;
[1;31mError: Transaction is already completed. (state=25000,code=0)[m
java.sql.SQLException: Transaction is already completed.
at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:764)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
at sqlline.Commands.execute(Commands.java:823)
at sqlline.Commands.sql(Commands.java:733)
at sqlline.SqlLine.dispatch(SqlLine.java:795)
at sqlline.SqlLine.begin(SqlLine.java:668)
at sqlline.SqlLine.start(SqlLine.java:373)
at sqlline.SqlLine.main(SqlLine.java:265)
{code}
Exception in node logs:
{code}
[17:44:36,234][SEVERE][jdbc-request-handler-worker-#61][JdbcRequestHandler]
Failed to execute SQL query [reqId=0, req=JdbcQueryExecuteRequest
[schemaName=PUBLIC, pageSize=1024, maxRows=0, sqlQry=select * from test,
args=Object[] [], stmtType=ANY_STATEMENT_TYPE, autoCommit=false]]
class org.apache.ignite.internal.processors.query.IgniteSQLException:
Transaction is already completed.
at
org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.checkActive(MvccUtils.java:623)
at
org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.requestSnapshot(MvccUtils.java:780)
at
org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.mvccTracker(MvccUtils.java:761)
at
org.apache.ignite.internal.processors.cache.mvcc.MvccUtils.mvccTracker(MvccUtils.java:744)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.runQueryTwoStep(IgniteH2Indexing.java:1731)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.doRunDistributedQuery(IgniteH2Indexing.java:2521)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.querySqlFields(IgniteH2Indexing.java:2074)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2139)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2134)
at
org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2711)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2148)
at
org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.executeQuery(JdbcRequestHandler.java:511)
at
org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.doHandle(JdbcRequestHandler.java:245)
at
org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandlerWorker.body(JdbcRequestHandlerWorker.java:90)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:748)
{code}
Works for any query which are throwing mvcc missmatch exception
After commit select query works again
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9541) Add the comparison for two general statistics "RunAll" for master in the date interval
[
https://issues.apache.org/jira/browse/IGNITE-9541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617667#comment-16617667
]
ASF GitHub Bot commented on IGNITE-9541:
SomeFire commented on a change in pull request #9: IGNITE-9541 Add the
comparison for two general statistics "RunAll" for master in the date interval
URL: https://github.com/apache/ignite-teamcity-bot/pull/9#discussion_r218100191
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/web/model/current/BuildStatisticsSummary.java
##
@@ -0,0 +1,293 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.ignite.ci.web.model.current;
+
+import java.text.DateFormat;
+import java.text.ParseException;
+import java.text.SimpleDateFormat;
+import java.util.ArrayList;
+import java.util.Date;
+import java.util.HashMap;
+import java.util.List;
+import java.util.Map;
+import java.util.Objects;
+import java.util.stream.Collectors;
+import java.util.stream.Stream;
+import javax.annotation.Nonnull;
+import org.apache.ignite.ci.ITeamcity;
+import org.apache.ignite.ci.tcmodel.hist.BuildRef;
+import org.apache.ignite.ci.tcmodel.result.Build;
+import org.apache.ignite.ci.tcmodel.result.TestOccurrencesRef;
+import org.apache.ignite.ci.tcmodel.result.issues.IssueRef;
+import org.apache.ignite.ci.tcmodel.result.issues.IssueUsage;
+import org.apache.ignite.ci.tcmodel.result.problems.ProblemOccurrence;
+import org.apache.ignite.ci.util.TimeUtil;
+import org.apache.ignite.ci.web.IBackgroundUpdatable;
+
+/**
+ * Summary of build statistics.
+ */
+public class BuildStatisticsSummary extends UpdateInfo implements
IBackgroundUpdatable {
+/** Short problem names. */
+public static final String TOTAL = "TOTAL";
+
+private static Map shortProblemNames = new HashMap<>();
+
+static {
+shortProblemNames.put(TOTAL, "TT");
+shortProblemNames.put(ProblemOccurrence.TC_EXECUTION_TIMEOUT, "ET");
+shortProblemNames.put(ProblemOccurrence.TC_JVM_CRASH, "JC");
+shortProblemNames.put(ProblemOccurrence.TC_OOME, "OO");
+shortProblemNames.put(ProblemOccurrence.TC_EXIT_CODE, "EC");
+shortProblemNames.put(ProblemOccurrence.TC_FAILED_TESTS, "FT");
+shortProblemNames.put(ProblemOccurrence.SNAPSHOT_DEPENDENCY_ERROR,
"SD");
+shortProblemNames.put(ProblemOccurrence.OTHER, "OT");
+}
+
+/** Build with test and problems references. */
+public Integer buildId;
+
+public String date;
+
+/** Test occurrences. */
+public TestOccurrencesRef testOccurrences;
+
+/** List of problem occurrences. */
+private List problemOccurrenceList;
+
+/** Snapshot-dependencies build run result. */
+public Map> dependenciesProblems;
+
+/** List of related issues. */
+private List relatedIssues;
+
+/** Duration printable. */
+public String durationPrintable;
+
+/** Short build run result (without snapshot-dependencies printable
result). */
+public Map totalProblems;
+
+/** Build problems count. */
+public long problemsCount;
+
+/** Is fake stub. */
+public boolean isFakeStub;
+
+/**
+ * @param buildId Build id.
+ */
+public BuildStatisticsSummary(Integer buildId){
+this.buildId = buildId;
+}
+
+/** Initialize build statistics. */
+public void initialize(@Nonnull final ITeamcity teamcity) {
+Build build = teamcity.getBuild(buildId);
+
+DateFormat dateFormat = new SimpleDateFormat("dd-MM-'T'HH:mm:ss");
+dateFormat.format(build.getFinishDate());
+date = dateFormat.format(build.getFinishDate());
+
+isFakeStub = build.isFakeStub();
+
+if (isFakeStub)
+return;
+
+testOccurrences = build.testOccurrences;
+
+relatedIssues =
teamcity.getIssuesUsagesList(build.relatedIssuesRef.href).getIssuesUsagesNonNull().stream()
+.map(IssueUsage::getIssue).collect(Collectors.toList());
+
+durationPrintable = TimeUtil
+.getDurationPrintable(build.getFinishDate().getTime() -
build.getStartDate().getTime());
+
+List snapshotDependencies =
[jira] [Commented] (IGNITE-9541) Add the comparison for two general statistics "RunAll" for master in the date interval
[
https://issues.apache.org/jira/browse/IGNITE-9541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617665#comment-16617665
]
ASF GitHub Bot commented on IGNITE-9541:
SomeFire commented on a change in pull request #9: IGNITE-9541 Add the
comparison for two general statistics "RunAll" for master in the date interval
URL: https://github.com/apache/ignite-teamcity-bot/pull/9#discussion_r218099174
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/tcmodel/result/issues/IssueUsage.java
##
@@ -0,0 +1,43 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.ignite.ci.tcmodel.result.issues;
+
+import javax.xml.bind.annotation.XmlAccessType;
+import javax.xml.bind.annotation.XmlAccessorType;
+import javax.xml.bind.annotation.XmlElement;
+import javax.xml.bind.annotation.XmlRootElement;
+import org.apache.ignite.ci.tcmodel.changes.ChangesList;
+
+/**
+ * Build's related issue from TC.
+ *
+ * See example of XML, e.g. here
+ * https://ci.ignite.apache.org/app/rest/latest/builds/id:1694977/relatedIssues
+ */
+@XmlRootElement(name = "IssueUsage")
+@XmlAccessorType(XmlAccessType.FIELD)
+public class IssueUsage {
+@XmlElement(name = "issue")
+private IssueRef issue;
+@XmlElement(name = "changes")
+private ChangesList changesList;
+
+public IssueRef getIssue(){
Review comment:
Missed javadoc.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Add the comparison for two general statistics "RunAll" for master in the date
> interval
> --
>
> Key: IGNITE-9541
> URL: https://issues.apache.org/jira/browse/IGNITE-9541
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Major
>
> Based on IGNITE-9333 add the comparison for two general statistics "RunAll"
> for master in the date interval
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9541) Add the comparison for two general statistics "RunAll" for master in the date interval
[
https://issues.apache.org/jira/browse/IGNITE-9541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617659#comment-16617659
]
ASF GitHub Bot commented on IGNITE-9541:
SomeFire commented on a change in pull request #9: IGNITE-9541 Add the
comparison for two general statistics "RunAll" for master in the date interval
URL: https://github.com/apache/ignite-teamcity-bot/pull/9#discussion_r218100329
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/web/model/current/BuildStatisticsSummary.java
##
@@ -0,0 +1,293 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.ignite.ci.web.model.current;
+
+import java.text.DateFormat;
+import java.text.ParseException;
+import java.text.SimpleDateFormat;
+import java.util.ArrayList;
+import java.util.Date;
+import java.util.HashMap;
+import java.util.List;
+import java.util.Map;
+import java.util.Objects;
+import java.util.stream.Collectors;
+import java.util.stream.Stream;
+import javax.annotation.Nonnull;
+import org.apache.ignite.ci.ITeamcity;
+import org.apache.ignite.ci.tcmodel.hist.BuildRef;
+import org.apache.ignite.ci.tcmodel.result.Build;
+import org.apache.ignite.ci.tcmodel.result.TestOccurrencesRef;
+import org.apache.ignite.ci.tcmodel.result.issues.IssueRef;
+import org.apache.ignite.ci.tcmodel.result.issues.IssueUsage;
+import org.apache.ignite.ci.tcmodel.result.problems.ProblemOccurrence;
+import org.apache.ignite.ci.util.TimeUtil;
+import org.apache.ignite.ci.web.IBackgroundUpdatable;
+
+/**
+ * Summary of build statistics.
+ */
+public class BuildStatisticsSummary extends UpdateInfo implements
IBackgroundUpdatable {
+/** Short problem names. */
+public static final String TOTAL = "TOTAL";
+
+private static Map shortProblemNames = new HashMap<>();
+
+static {
+shortProblemNames.put(TOTAL, "TT");
+shortProblemNames.put(ProblemOccurrence.TC_EXECUTION_TIMEOUT, "ET");
+shortProblemNames.put(ProblemOccurrence.TC_JVM_CRASH, "JC");
+shortProblemNames.put(ProblemOccurrence.TC_OOME, "OO");
+shortProblemNames.put(ProblemOccurrence.TC_EXIT_CODE, "EC");
+shortProblemNames.put(ProblemOccurrence.TC_FAILED_TESTS, "FT");
+shortProblemNames.put(ProblemOccurrence.SNAPSHOT_DEPENDENCY_ERROR,
"SD");
+shortProblemNames.put(ProblemOccurrence.OTHER, "OT");
+}
+
+/** Build with test and problems references. */
+public Integer buildId;
+
+public String date;
+
+/** Test occurrences. */
+public TestOccurrencesRef testOccurrences;
+
+/** List of problem occurrences. */
+private List problemOccurrenceList;
+
+/** Snapshot-dependencies build run result. */
+public Map> dependenciesProblems;
+
+/** List of related issues. */
+private List relatedIssues;
+
+/** Duration printable. */
+public String durationPrintable;
+
+/** Short build run result (without snapshot-dependencies printable
result). */
+public Map totalProblems;
+
+/** Build problems count. */
+public long problemsCount;
+
+/** Is fake stub. */
+public boolean isFakeStub;
+
+/**
+ * @param buildId Build id.
+ */
+public BuildStatisticsSummary(Integer buildId){
+this.buildId = buildId;
+}
+
+/** Initialize build statistics. */
+public void initialize(@Nonnull final ITeamcity teamcity) {
+Build build = teamcity.getBuild(buildId);
+
+DateFormat dateFormat = new SimpleDateFormat("dd-MM-'T'HH:mm:ss");
+dateFormat.format(build.getFinishDate());
+date = dateFormat.format(build.getFinishDate());
+
+isFakeStub = build.isFakeStub();
+
+if (isFakeStub)
+return;
+
+testOccurrences = build.testOccurrences;
+
+relatedIssues =
teamcity.getIssuesUsagesList(build.relatedIssuesRef.href).getIssuesUsagesNonNull().stream()
+.map(IssueUsage::getIssue).collect(Collectors.toList());
+
+durationPrintable = TimeUtil
+.getDurationPrintable(build.getFinishDate().getTime() -
build.getStartDate().getTime());
+
+List snapshotDependencies =
[jira] [Commented] (IGNITE-9541) Add the comparison for two general statistics "RunAll" for master in the date interval
[
https://issues.apache.org/jira/browse/IGNITE-9541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617651#comment-16617651
]
ASF GitHub Bot commented on IGNITE-9541:
SomeFire commented on a change in pull request #9: IGNITE-9541 Add the
comparison for two general statistics "RunAll" for master in the date interval
URL: https://github.com/apache/ignite-teamcity-bot/pull/9#discussion_r218100491
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/web/model/current/BuildStatisticsSummary.java
##
@@ -0,0 +1,293 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.ignite.ci.web.model.current;
+
+import java.text.DateFormat;
+import java.text.ParseException;
+import java.text.SimpleDateFormat;
+import java.util.ArrayList;
+import java.util.Date;
+import java.util.HashMap;
+import java.util.List;
+import java.util.Map;
+import java.util.Objects;
+import java.util.stream.Collectors;
+import java.util.stream.Stream;
+import javax.annotation.Nonnull;
+import org.apache.ignite.ci.ITeamcity;
+import org.apache.ignite.ci.tcmodel.hist.BuildRef;
+import org.apache.ignite.ci.tcmodel.result.Build;
+import org.apache.ignite.ci.tcmodel.result.TestOccurrencesRef;
+import org.apache.ignite.ci.tcmodel.result.issues.IssueRef;
+import org.apache.ignite.ci.tcmodel.result.issues.IssueUsage;
+import org.apache.ignite.ci.tcmodel.result.problems.ProblemOccurrence;
+import org.apache.ignite.ci.util.TimeUtil;
+import org.apache.ignite.ci.web.IBackgroundUpdatable;
+
+/**
+ * Summary of build statistics.
+ */
+public class BuildStatisticsSummary extends UpdateInfo implements
IBackgroundUpdatable {
+/** Short problem names. */
+public static final String TOTAL = "TOTAL";
+
+private static Map shortProblemNames = new HashMap<>();
+
+static {
+shortProblemNames.put(TOTAL, "TT");
+shortProblemNames.put(ProblemOccurrence.TC_EXECUTION_TIMEOUT, "ET");
+shortProblemNames.put(ProblemOccurrence.TC_JVM_CRASH, "JC");
+shortProblemNames.put(ProblemOccurrence.TC_OOME, "OO");
+shortProblemNames.put(ProblemOccurrence.TC_EXIT_CODE, "EC");
+shortProblemNames.put(ProblemOccurrence.TC_FAILED_TESTS, "FT");
+shortProblemNames.put(ProblemOccurrence.SNAPSHOT_DEPENDENCY_ERROR,
"SD");
+shortProblemNames.put(ProblemOccurrence.OTHER, "OT");
+}
+
+/** Build with test and problems references. */
+public Integer buildId;
+
+public String date;
+
+/** Test occurrences. */
+public TestOccurrencesRef testOccurrences;
+
+/** List of problem occurrences. */
+private List problemOccurrenceList;
+
+/** Snapshot-dependencies build run result. */
+public Map> dependenciesProblems;
+
+/** List of related issues. */
+private List relatedIssues;
+
+/** Duration printable. */
+public String durationPrintable;
+
+/** Short build run result (without snapshot-dependencies printable
result). */
+public Map totalProblems;
+
+/** Build problems count. */
+public long problemsCount;
+
+/** Is fake stub. */
+public boolean isFakeStub;
+
+/**
+ * @param buildId Build id.
+ */
+public BuildStatisticsSummary(Integer buildId){
+this.buildId = buildId;
+}
+
+/** Initialize build statistics. */
+public void initialize(@Nonnull final ITeamcity teamcity) {
+Build build = teamcity.getBuild(buildId);
+
+DateFormat dateFormat = new SimpleDateFormat("dd-MM-'T'HH:mm:ss");
+dateFormat.format(build.getFinishDate());
+date = dateFormat.format(build.getFinishDate());
+
+isFakeStub = build.isFakeStub();
+
+if (isFakeStub)
+return;
+
+testOccurrences = build.testOccurrences;
+
+relatedIssues =
teamcity.getIssuesUsagesList(build.relatedIssuesRef.href).getIssuesUsagesNonNull().stream()
+.map(IssueUsage::getIssue).collect(Collectors.toList());
+
+durationPrintable = TimeUtil
+.getDurationPrintable(build.getFinishDate().getTime() -
build.getStartDate().getTime());
+
+List snapshotDependencies =
[jira] [Commented] (IGNITE-9541) Add the comparison for two general statistics "RunAll" for master in the date interval
[
https://issues.apache.org/jira/browse/IGNITE-9541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617647#comment-16617647
]
ASF GitHub Bot commented on IGNITE-9541:
SomeFire commented on a change in pull request #9: IGNITE-9541 Add the
comparison for two general statistics "RunAll" for master in the date interval
URL: https://github.com/apache/ignite-teamcity-bot/pull/9#discussion_r218091389
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/ITeamcity.java
##
@@ -52,6 +54,7 @@
public interface ITeamcity extends AutoCloseable {
String DEFAULT = "";
+long DEFAULT_BUILDS_COUNT = 1000;
Review comment:
Missec javadoc. Need empty line before previous field.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Add the comparison for two general statistics "RunAll" for master in the date
> interval
> --
>
> Key: IGNITE-9541
> URL: https://issues.apache.org/jira/browse/IGNITE-9541
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Major
>
> Based on IGNITE-9333 add the comparison for two general statistics "RunAll"
> for master in the date interval
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9541) Add the comparison for two general statistics "RunAll" for master in the date interval
[
https://issues.apache.org/jira/browse/IGNITE-9541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617653#comment-16617653
]
ASF GitHub Bot commented on IGNITE-9541:
SomeFire commented on a change in pull request #9: IGNITE-9541 Add the
comparison for two general statistics "RunAll" for master in the date interval
URL: https://github.com/apache/ignite-teamcity-bot/pull/9#discussion_r218102209
##
File path: ignite-tc-helper-web/src/main/webapp/css/style-1.5.css
##
@@ -115,4 +115,33 @@ form li:after
clear:both;
display:block;
margin-top:10px;
+}
+.stat{
Review comment:
Missed blank lines between styles.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Add the comparison for two general statistics "RunAll" for master in the date
> interval
> --
>
> Key: IGNITE-9541
> URL: https://issues.apache.org/jira/browse/IGNITE-9541
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Major
>
> Based on IGNITE-9333 add the comparison for two general statistics "RunAll"
> for master in the date interval
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9541) Add the comparison for two general statistics "RunAll" for master in the date interval
[
https://issues.apache.org/jira/browse/IGNITE-9541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617641#comment-16617641
]
ASF GitHub Bot commented on IGNITE-9541:
SomeFire commented on a change in pull request #9: IGNITE-9541 Add the
comparison for two general statistics "RunAll" for master in the date interval
URL: https://github.com/apache/ignite-teamcity-bot/pull/9#discussion_r218090321
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/ITeamcity.java
##
@@ -62,7 +65,19 @@
* @param branch
* @return list of builds in historical order, recent builds coming last
*/
-List getFinishedBuilds(String projectId, String branch);
+default List getFinishedBuilds(String projectId, String branch) {
+return getFinishedBuilds(projectId, branch, null, null);
+};
+
+/**
+ * @param projectId suite ID (string without spaces)
+ * @param branch
+ * @param sinceDate
+ * @param untilDate
+ * @return list of builds in historical order, recent builds coming last
+ */
+
Review comment:
Remove empty line.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Add the comparison for two general statistics "RunAll" for master in the date
> interval
> --
>
> Key: IGNITE-9541
> URL: https://issues.apache.org/jira/browse/IGNITE-9541
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Major
>
> Based on IGNITE-9333 add the comparison for two general statistics "RunAll"
> for master in the date interval
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9541) Add the comparison for two general statistics "RunAll" for master in the date interval
[
https://issues.apache.org/jira/browse/IGNITE-9541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617642#comment-16617642
]
ASF GitHub Bot commented on IGNITE-9541:
SomeFire commented on a change in pull request #9: IGNITE-9541 Add the
comparison for two general statistics "RunAll" for master in the date interval
URL: https://github.com/apache/ignite-teamcity-bot/pull/9#discussion_r218091720
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/IgnitePersistentTeamcity.java
##
@@ -197,7 +203,7 @@ private IgnitePersistentTeamcity(Ignite ignite,
IgniteTeamcityHelper teamcity) {
}
/**
- * @return Build history: {@link BuildRef} lists cache, 32 parts,
transaactional
+ * @return Build history: {@link BuildRef} lists cache, 32 parts,
transactional
Review comment:
Missed dot at the end of sentence.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Add the comparison for two general statistics "RunAll" for master in the date
> interval
> --
>
> Key: IGNITE-9541
> URL: https://issues.apache.org/jira/browse/IGNITE-9541
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Major
>
> Based on IGNITE-9333 add the comparison for two general statistics "RunAll"
> for master in the date interval
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9541) Add the comparison for two general statistics "RunAll" for master in the date interval
[
https://issues.apache.org/jira/browse/IGNITE-9541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617654#comment-16617654
]
ASF GitHub Bot commented on IGNITE-9541:
SomeFire commented on a change in pull request #9: IGNITE-9541 Add the
comparison for two general statistics "RunAll" for master in the date interval
URL: https://github.com/apache/ignite-teamcity-bot/pull/9#discussion_r218097013
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/IgniteTeamcityHelper.java
##
@@ -409,12 +444,12 @@ public ChangesList getChangesList(String href) {
}
/** {@inheritDoc} */
-@Override public List getFinishedBuilds(String projectId,
-String branch) {
+public List getFinishedBuilds(String projectId,
+String branch, Date sinceDate, Date untilDate) {
List finished = getBuildHistory(projectId,
UrlUtil.escape(branch),
true,
-null);
+null, sinceDate, untilDate);
Review comment:
Move args to the new lines.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Add the comparison for two general statistics "RunAll" for master in the date
> interval
> --
>
> Key: IGNITE-9541
> URL: https://issues.apache.org/jira/browse/IGNITE-9541
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Major
>
> Based on IGNITE-9333 add the comparison for two general statistics "RunAll"
> for master in the date interval
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9541) Add the comparison for two general statistics "RunAll" for master in the date interval
[ https://issues.apache.org/jira/browse/IGNITE-9541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617648#comment-16617648 ] ASF GitHub Bot commented on IGNITE-9541: SomeFire commented on a change in pull request #9: IGNITE-9541 Add the comparison for two general statistics "RunAll" for master in the date interval URL: https://github.com/apache/ignite-teamcity-bot/pull/9#discussion_r218098330 ## File path: ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/tcmodel/hist/BuildRef.java ## @@ -52,6 +52,8 @@ @XmlAttribute public Boolean composite; +@XmlAttribute public String webUrl; Review comment: Rebase your branch on current master. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Add the comparison for two general statistics "RunAll" for master in the date > interval > -- > > Key: IGNITE-9541 > URL: https://issues.apache.org/jira/browse/IGNITE-9541 > Project: Ignite > Issue Type: Sub-task >Reporter: Nikolai Kulagin >Assignee: Nikolai Kulagin >Priority: Major > > Based on IGNITE-9333 add the comparison for two general statistics "RunAll" > for master in the date interval -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9541) Add the comparison for two general statistics "RunAll" for master in the date interval
[
https://issues.apache.org/jira/browse/IGNITE-9541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617670#comment-16617670
]
ASF GitHub Bot commented on IGNITE-9541:
SomeFire commented on a change in pull request #9: IGNITE-9541 Add the
comparison for two general statistics "RunAll" for master in the date interval
URL: https://github.com/apache/ignite-teamcity-bot/pull/9#discussion_r218100964
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/web/rest/build/GetBuildTestFailures.java
##
@@ -149,4 +153,71 @@ public TestFailuresSummary getBuildTestFails(
return res;
}
+
+@GET
+@Path("history")
+public List getBuildsHistory(
+@Nullable @QueryParam("server") String server,
+@Nullable @QueryParam("buildType") String buildType,
+@Nullable @QueryParam("branch") String branch,
+@Nullable @QueryParam("sinceDate") String sinceDate,
+@Nullable @QueryParam("untilDate") String untilDate)
+throws ServiceUnauthorizedException, ParseException {
+
+DateFormat dateFormat = new SimpleDateFormat("ddMMHHmmss");
+
+String srvId = isNullOrEmpty(server) ? "apache" : server;
+String buildTypeId = isNullOrEmpty(buildType) ?
"IgniteTests24Java8_RunAll" : buildType;
+String branchName = isNullOrEmpty(branch) ? "refs/heads/master" :
branch;
+Date sinceDateFilter = isNullOrEmpty(sinceDate) ? null :
dateFormat.parse(sinceDate);
+Date untilDateFilter = isNullOrEmpty(untilDate) ? null :
dateFormat.parse(untilDate);
+
+final BackgroundUpdater updater =
CtxListener.getBackgroundUpdater(context);
+
+final ITcHelper tcHelper = CtxListener.getTcHelper(context);
+
+final ICredentialsProv prov = ICredentialsProv.get(req);
+
+try (IAnalyticsEnabledTeamcity teamcity = tcHelper.server(srvId,
prov)) {
+
+int[] finishedBuilds =
teamcity.getBuildNumbersFromHistory(buildTypeId, branchName, sinceDateFilter,
untilDateFilter);
+
+List buildsStatistics = new ArrayList<>();
+
+for (int i = 0; i < finishedBuilds.length; i++) {
+int buildId = finishedBuilds[i];
+
+FullQueryParams param = new FullQueryParams();
+param.setBuildId(buildId);
+param.setBranch(branchName);
+param.setServerId(srvId);
+
+BuildStatisticsSummary buildsStatistic = updater.get(
+BUILDS_STATISTICS_SUMMARY_CACHE_NAME, prov, param,
+(k) -> getBuildStatisticsSummaryNoCache(srvId, buildId),
false);
+
+if (!buildsStatistic.isFakeStub)
+buildsStatistics.add(buildsStatistic);
+}
+
+return buildsStatistics;
+}
+}
+
+private BuildStatisticsSummary getBuildStatisticsSummaryNoCache(String
server, int buildId) {
+
Review comment:
Redundant blank line.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Add the comparison for two general statistics "RunAll" for master in the date
> interval
> --
>
> Key: IGNITE-9541
> URL: https://issues.apache.org/jira/browse/IGNITE-9541
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Major
>
> Based on IGNITE-9333 add the comparison for two general statistics "RunAll"
> for master in the date interval
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9541) Add the comparison for two general statistics "RunAll" for master in the date interval
[
https://issues.apache.org/jira/browse/IGNITE-9541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617666#comment-16617666
]
ASF GitHub Bot commented on IGNITE-9541:
SomeFire commented on a change in pull request #9: IGNITE-9541 Add the
comparison for two general statistics "RunAll" for master in the date interval
URL: https://github.com/apache/ignite-teamcity-bot/pull/9#discussion_r218102782
##
File path: ignite-tc-helper-web/src/main/webapp/statistics.html
##
@@ -0,0 +1,213 @@
+
+
+Ignite Teamcity - statistics master's branch
+
+https://code.jquery.com/ui/1.12.1/themes/base/jquery-ui.css;>
+
+
+https://code.jquery.com/jquery-1.12.4.js";>
+https://code.jquery.com/ui/1.12.1/jquery-ui.js";>
+
+
+
+table {
+width: 70%;
+border-collapse: collapse;
+}
+td, th {
+
+padding: 10px 5px 10px 5px;
+}
+th {
+text-align: left;
+padding: 5px;
+background-color: #f5f5ff;
+color: #00;
+}
+tr:nth-child(odd) { background-color: #fafaff; }
+
+
+
[jira] [Commented] (IGNITE-9541) Add the comparison for two general statistics "RunAll" for master in the date interval
[
https://issues.apache.org/jira/browse/IGNITE-9541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617649#comment-16617649
]
ASF GitHub Bot commented on IGNITE-9541:
SomeFire commented on a change in pull request #9: IGNITE-9541 Add the
comparison for two general statistics "RunAll" for master in the date interval
URL: https://github.com/apache/ignite-teamcity-bot/pull/9#discussion_r218097631
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/IgniteTeamcityHelper.java
##
@@ -409,12 +444,12 @@ public ChangesList getChangesList(String href) {
}
/** {@inheritDoc} */
-@Override public List getFinishedBuilds(String projectId,
-String branch) {
+public List getFinishedBuilds(String projectId,
+String branch, Date sinceDate, Date untilDate) {
Review comment:
Place all args on the same line or different lines.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Add the comparison for two general statistics "RunAll" for master in the date
> interval
> --
>
> Key: IGNITE-9541
> URL: https://issues.apache.org/jira/browse/IGNITE-9541
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Major
>
> Based on IGNITE-9333 add the comparison for two general statistics "RunAll"
> for master in the date interval
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9541) Add the comparison for two general statistics "RunAll" for master in the date interval
[
https://issues.apache.org/jira/browse/IGNITE-9541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617652#comment-16617652
]
ASF GitHub Bot commented on IGNITE-9541:
SomeFire commented on a change in pull request #9: IGNITE-9541 Add the
comparison for two general statistics "RunAll" for master in the date interval
URL: https://github.com/apache/ignite-teamcity-bot/pull/9#discussion_r218096032
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/IgnitePersistentTeamcity.java
##
@@ -591,6 +625,24 @@ private void addTestOccurrencesToStat(TestOccurrences
val, String normalizedBran
});
}
+@Override public IssuesUsagesList getIssuesUsagesList(String href) {
Review comment:
Missec javadoc.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Add the comparison for two general statistics "RunAll" for master in the date
> interval
> --
>
> Key: IGNITE-9541
> URL: https://issues.apache.org/jira/browse/IGNITE-9541
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Major
>
> Based on IGNITE-9333 add the comparison for two general statistics "RunAll"
> for master in the date interval
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9541) Add the comparison for two general statistics "RunAll" for master in the date interval
[
https://issues.apache.org/jira/browse/IGNITE-9541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617656#comment-16617656
]
ASF GitHub Bot commented on IGNITE-9541:
SomeFire commented on a change in pull request #9: IGNITE-9541 Add the
comparison for two general statistics "RunAll" for master in the date interval
URL: https://github.com/apache/ignite-teamcity-bot/pull/9#discussion_r218099233
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/tcmodel/result/issues/IssuesUsagesList.java
##
@@ -0,0 +1,49 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.ignite.ci.tcmodel.result.issues;
+
+import java.util.Collections;
+import java.util.List;
+import javax.xml.bind.annotation.XmlElement;
+import javax.xml.bind.annotation.XmlRootElement;
+
+/**
+ * List of build's related issues from TC.
+ *
+ * See example of XML, e.g. here
+ * https://ci.ignite.apache.org/app/rest/latest/builds/id:1694977/relatedIssues
+ */
+@XmlRootElement(name = "issuesUsages")
+public class IssuesUsagesList {
+@XmlElement(name = "issueUsage")
+private List issuesUsages;
+
+@XmlElement Integer count;
+
+@XmlElement String href;
+
+public List getIssuesUsagesNonNull() {
+return issuesUsages == null ? Collections.emptyList() : issuesUsages;
+}
+
+@Override public String toString() {
Review comment:
Missed javadoc.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Add the comparison for two general statistics "RunAll" for master in the date
> interval
> --
>
> Key: IGNITE-9541
> URL: https://issues.apache.org/jira/browse/IGNITE-9541
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Major
>
> Based on IGNITE-9333 add the comparison for two general statistics "RunAll"
> for master in the date interval
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9541) Add the comparison for two general statistics "RunAll" for master in the date interval
[
https://issues.apache.org/jira/browse/IGNITE-9541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617650#comment-16617650
]
ASF GitHub Bot commented on IGNITE-9541:
SomeFire commented on a change in pull request #9: IGNITE-9541 Add the
comparison for two general statistics "RunAll" for master in the date interval
URL: https://github.com/apache/ignite-teamcity-bot/pull/9#discussion_r218095484
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/IgnitePersistentTeamcity.java
##
@@ -290,6 +300,26 @@ private IgnitePersistentTeamcity(Ignite ignite,
IgniteTeamcityHelper teamcity) {
return mergeByIdToHistoricalOrder(persistedValue, builds);
});
+
+if (sinceDate != null && untilDate != null)
Review comment:
Is it possible to get request with `sinceDate` and without `untilDate`? And
vice versa?
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Add the comparison for two general statistics "RunAll" for master in the date
> interval
> --
>
> Key: IGNITE-9541
> URL: https://issues.apache.org/jira/browse/IGNITE-9541
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Major
>
> Based on IGNITE-9333 add the comparison for two general statistics "RunAll"
> for master in the date interval
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9541) Add the comparison for two general statistics "RunAll" for master in the date interval
[
https://issues.apache.org/jira/browse/IGNITE-9541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617643#comment-16617643
]
ASF GitHub Bot commented on IGNITE-9541:
SomeFire commented on a change in pull request #9: IGNITE-9541 Add the
comparison for two general statistics "RunAll" for master in the date interval
URL: https://github.com/apache/ignite-teamcity-bot/pull/9#discussion_r218090754
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/ITeamcity.java
##
@@ -62,7 +65,19 @@
* @param branch
* @return list of builds in historical order, recent builds coming last
*/
-List getFinishedBuilds(String projectId, String branch);
+default List getFinishedBuilds(String projectId, String branch) {
+return getFinishedBuilds(projectId, branch, null, null);
+};
+
+/**
+ * @param projectId suite ID (string without spaces)
+ * @param branch
Review comment:
Missed param description.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Add the comparison for two general statistics "RunAll" for master in the date
> interval
> --
>
> Key: IGNITE-9541
> URL: https://issues.apache.org/jira/browse/IGNITE-9541
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Major
>
> Based on IGNITE-9333 add the comparison for two general statistics "RunAll"
> for master in the date interval
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9541) Add the comparison for two general statistics "RunAll" for master in the date interval
[
https://issues.apache.org/jira/browse/IGNITE-9541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617646#comment-16617646
]
ASF GitHub Bot commented on IGNITE-9541:
SomeFire commented on a change in pull request #9: IGNITE-9541 Add the
comparison for two general statistics "RunAll" for master in the date interval
URL: https://github.com/apache/ignite-teamcity-bot/pull/9#discussion_r218098809
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/tcmodel/result/Build.java
##
@@ -127,4 +137,4 @@ public Triggered getTriggered() {
public void setTriggered(Triggered triggered) {
this.triggered = triggered;
}
-}
+}
Review comment:
File should ends with a blank line.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Add the comparison for two general statistics "RunAll" for master in the date
> interval
> --
>
> Key: IGNITE-9541
> URL: https://issues.apache.org/jira/browse/IGNITE-9541
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Major
>
> Based on IGNITE-9333 add the comparison for two general statistics "RunAll"
> for master in the date interval
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9492) Refactor processing SingleMessage with exchangeId==null
[ https://issues.apache.org/jira/browse/IGNITE-9492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617632#comment-16617632 ] ASF GitHub Bot commented on IGNITE-9492: GitHub user Jokser opened a pull request: https://github.com/apache/ignite/pull/4773 IGNITE-9492 Ignore SingleMessage updated where there is in-progress exchange …rogress. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9492 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4773.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4773 commit 0d0a25364eb4dfa97f57e98fa56e1e996476c604 Author: Pavel Kovalenko Date: 2018-09-17T14:46:45Z IGNITE-9492 Ignore SingleMessage updated where there is exchange in progress. > Refactor processing SingleMessage with exchangeId==null > --- > > Key: IGNITE-9492 > URL: https://issues.apache.org/jira/browse/IGNITE-9492 > Project: Ignite > Issue Type: Improvement > Components: cache >Affects Versions: 2.5 >Reporter: Pavel Kovalenko >Assignee: Pavel Kovalenko >Priority: Major > Fix For: 2.7 > > > Currently, after each PME coordinator spend a lot of time on processing > correcting Single messages (with exchange id == null). This leads to growing > inbound/outbound messages queue and delaying other coordinator-aware > processes. > Processing single messages with exchange id == null are not so important to > give all available resources to it. We should limit the number of sys-threads > which are able to process such single messages. > We shouldn't create a big SingleMessages for each of partition state change > and use more shrinked/tiny messages for that. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-9487) REST: getall can only output keys as scalars
[
https://issues.apache.org/jira/browse/IGNITE-9487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Kasnacheev closed IGNITE-9487.
---
> REST: getall can only output keys as scalars
>
>
> Key: IGNITE-9487
> URL: https://issues.apache.org/jira/browse/IGNITE-9487
> Project: Ignite
> Issue Type: Improvement
> Components: rest
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Major
> Fix For: 2.7
>
>
> Regardless of what ConnectorMessageInterceptor does, `getall' command can
> only output key as string or number, and not as JSON object as values can.
> This is because output format is as follows:
> {code}
> {"successStatus":0,"affinityNodeId":null,"sessionToken":null,"response":{"CustomType
> [idHash=1588995554, hash=34706515, key=111]":{"val":"111"},"CustomType
> [idHash=978025370, hash=30386820, key=222]":{"val":"222"}},"error":null}
> {code}
> The desired output format may look like:
> {code}
> {"successStatus":0,"affinityNodeId":null,"sessionToken":null,"response":[{"key":{"key":111},"value":{"val":"111"}},{"key":{"key":222},"value":{"val":"222"}}],"error":null}
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9619) Document REST "getall" array format
Ilya Kasnacheev created IGNITE-9619: --- Summary: Document REST "getall" array format Key: IGNITE-9619 URL: https://issues.apache.org/jira/browse/IGNITE-9619 Project: Ignite Issue Type: Improvement Components: documentation Reporter: Ilya Kasnacheev Fix For: 2.7 https://apacheignite.readme.io/docs/rest-api#get-all <-- this page should have a section about new IGNITE_REST_GETALL_AS_ARRAY System Property, as well as an example of response after it is set. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-5553) Ignite PDS 2: IgnitePersistentStoreDataStructuresTest testSet assertion error
[
https://issues.apache.org/jira/browse/IGNITE-5553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617613#comment-16617613
]
Ryabov Dmitrii commented on IGNITE-5553:
{panel:title=No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity Run
All|http://ci.ignite.apache.org/viewLog.html?buildId=1880784buildTypeId=IgniteTests24Java8_RunAll]
> Ignite PDS 2: IgnitePersistentStoreDataStructuresTest testSet assertion error
> -
>
> Key: IGNITE-5553
> URL: https://issues.apache.org/jira/browse/IGNITE-5553
> Project: Ignite
> Issue Type: Bug
> Components: data structures, persistence
>Affects Versions: 2.1
>Reporter: Dmitriy Pavlov
>Assignee: Pavel Pereslegin
>Priority: Major
> Labels: MakeTeamcityGreenAgain, Muted_test, test-fail
> Fix For: 2.7
>
>
> h2. Notes-4435
> When IgniteSet is restored from persistence, size of set is always 0, [link
> to test
> history|http://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=-7043871603266099589=testDetails].
> h2. Detailed description
> Unlike *IgniteQueue* which uses separate cache key to store its size
> *IgniteSet* stores it in a field of some class.
> Test from the link above shows very clearly that after restoring memory state
> from PDS all set values are restored correctly but size is lost.
> h2. Proposed solution
> One possible solution might be to do the same thing as *IgniteQueue* does:
> size of *IgniteSet* must be stored is cache instead of volatile in-memory
> fields of random classes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9519) PK as complex type should can be keep at inline index
[ https://issues.apache.org/jira/browse/IGNITE-9519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617603#comment-16617603 ] Stanislav Lukyanov commented on IGNITE-9519: Added test (BasicIndexTest). TC: https://ci.ignite.apache.org/viewLog.html?buildId=1889774=buildResultsDiv=IgniteTests24Java8_RunAll [~vozerov], please review. > PK as complex type should can be keep at inline index > - > > Key: IGNITE-9519 > URL: https://issues.apache.org/jira/browse/IGNITE-9519 > Project: Ignite > Issue Type: Improvement > Components: sql >Affects Versions: 2.6 >Reporter: Yury Gerzhedovich >Assignee: Stanislav Lukyanov >Priority: Major > > Currently in case PK is complex type it can not be keep at inline index. > This is critical performance issue due to for any put or get operation it > cant' be fully comparable and require read full object from the heap or even > disk storage. > To mitigate the problem we need add ability keep complex type (java object) > at inline indexes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9341) Notify metastorage listeners right before start of discovery processor
[ https://issues.apache.org/jira/browse/IGNITE-9341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617590#comment-16617590 ] Dmitriy Govorukhin commented on IGNITE-9341: [~slava.koptilin] Looks good to me. Thanks for the contribution. > Notify metastorage listeners right before start of discovery processor > -- > > Key: IGNITE-9341 > URL: https://issues.apache.org/jira/browse/IGNITE-9341 > Project: Ignite > Issue Type: Improvement > Components: general >Reporter: Ivan Rakov >Assignee: Vyacheslav Koptilin >Priority: Major > Fix For: 2.8 > > > onReadyForRead() is called only for inheritors of > MetastorageLifecycleListener interface which are started prior to > GridCacheProcessor. Listeners are notified at the moment of > ReadOnlyMetastorage initialization, which in turn occur during > GridCacheDatabaseSharedManager start. > We can split ReadOnlyMetastorage initialization and notification of listeners > - this will allow all components to subscribe for read-only metastorage ready > event. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9618) Need to be replace the data compression algorithm
Alexand Polyakov created IGNITE-9618: Summary: Need to be replace the data compression algorithm Key: IGNITE-9618 URL: https://issues.apache.org/jira/browse/IGNITE-9618 Project: Ignite Issue Type: New Feature Components: persistence Reporter: Alexand Polyakov Now used zip and its speed slow Exist alternatives and on tests in terms of performance they showed themselves to be better source file wal 1Gb result ||algoritm||time, ms||size, byte|| |zip|18 889|79 950 283| |[Snappy|https://github.com/xerial/snappy-java]|3 372|156 482 623| |[lz4|https://github.com/lz4/lz4-java]|2 047|128 591 795| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9487) REST: getall can only output keys as scalars
[
https://issues.apache.org/jira/browse/IGNITE-9487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617530#comment-16617530
]
ASF GitHub Bot commented on IGNITE-9487:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4756
> REST: getall can only output keys as scalars
>
>
> Key: IGNITE-9487
> URL: https://issues.apache.org/jira/browse/IGNITE-9487
> Project: Ignite
> Issue Type: Improvement
> Components: rest
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Major
> Fix For: 2.7
>
>
> Regardless of what ConnectorMessageInterceptor does, `getall' command can
> only output key as string or number, and not as JSON object as values can.
> This is because output format is as follows:
> {code}
> {"successStatus":0,"affinityNodeId":null,"sessionToken":null,"response":{"CustomType
> [idHash=1588995554, hash=34706515, key=111]":{"val":"111"},"CustomType
> [idHash=978025370, hash=30386820, key=222]":{"val":"222"}},"error":null}
> {code}
> The desired output format may look like:
> {code}
> {"successStatus":0,"affinityNodeId":null,"sessionToken":null,"response":[{"key":{"key":111},"value":{"val":"111"}},{"key":{"key":222},"value":{"val":"222"}}],"error":null}
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9487) REST: getall can only output keys as scalars
[
https://issues.apache.org/jira/browse/IGNITE-9487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Kuznetsov updated IGNITE-9487:
-
Fix Version/s: 2.7
> REST: getall can only output keys as scalars
>
>
> Key: IGNITE-9487
> URL: https://issues.apache.org/jira/browse/IGNITE-9487
> Project: Ignite
> Issue Type: Improvement
> Components: rest
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Major
> Fix For: 2.7
>
>
> Regardless of what ConnectorMessageInterceptor does, `getall' command can
> only output key as string or number, and not as JSON object as values can.
> This is because output format is as follows:
> {code}
> {"successStatus":0,"affinityNodeId":null,"sessionToken":null,"response":{"CustomType
> [idHash=1588995554, hash=34706515, key=111]":{"val":"111"},"CustomType
> [idHash=978025370, hash=30386820, key=222]":{"val":"222"}},"error":null}
> {code}
> The desired output format may look like:
> {code}
> {"successStatus":0,"affinityNodeId":null,"sessionToken":null,"response":[{"key":{"key":111},"value":{"val":"111"}},{"key":{"key":222},"value":{"val":"222"}}],"error":null}
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-9162) Query returns ICE: org.h2.table.TableView cannot be cast
[
https://issues.apache.org/jira/browse/IGNITE-9162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Grimstad reassigned IGNITE-9162:
---
Assignee: Sergey Grimstad
> Query returns ICE: org.h2.table.TableView cannot be cast
>
>
> Key: IGNITE-9162
> URL: https://issues.apache.org/jira/browse/IGNITE-9162
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.4
>Reporter: Sergey Kozlov
>Assignee: Sergey Grimstad
>Priority: Critical
> Fix For: 2.7
>
> Attachments: caches.xml, client.xml, policies.xml, server.xml
>
>
> 1. Start 1 Ignite node {{bin/ignite.sh server.xml -v -J-DCONSISTENT_ID=node1}}
> 2. Start sqlline {{bin/sqlline.sh -u
> jdbc:ignite:thin://127.0.0.1/?distributedJoins=true}}
> 3. Execute statements:
> {noformat}
> 0: jdbc:ignite:thin://127.0.0.1/> CREATE TABLE t1 ( id INT NOT NULL, int_col1
> INT NOT NULL, PRIMARY KEY (id)) WITH "TEMPLATE=partitioned";
> No rows affected (0,151 seconds)
> 0: jdbc:ignite:thin://127.0.0.1/> INSERT INTO t1 (id,int_col1) VALUES
> (1,0),(2,0),(3,0),(4,0);
> 4 rows affected (0,052 seconds)
> 0: jdbc:ignite:thin://127.0.0.1/> SELECT * FROM ( SELECT * FROM t1 WHERE
> int_col1 > 0 ORDER BY id ) WHERE int_col1 = 1
> ORDER BY id;
> Error: javax.cache.CacheException: class
> org.apache.ignite.IgniteCheckedException: org.h2.table.TableView cannot be
> cast
> to org.apache.ignite.internal.processors.query.h2.opt.GridH2Table
> (state=5,code=0)
> 0: jdbc:ignite:thin://127.0.0.1/>
> {noformat}
> Node log:
> {noformat}
> [12:39:38,162][SEVERE][client-connector-#50][JdbcRequestHandler] Failed to
> execute SQL query [reqId=0, req=JdbcQueryExecuteRequest [schemaName=PUBLIC,
> pageSize=1024, maxRows=0, sqlQry=SELECT * FROM ( SELECT * FROM t1 WHERE
> int_col1 > 0 ORDER BY id ) WHERE int_col1 = 1 ORDER BY id, args=[],
> stmtType=ANY_STATEMENT_TYPE]]
> javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException:
> org.h2.table.TableView cannot be cast to
> org.apache.ignite.internal.processors.query.h2.opt.GridH2Table
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2047)
> at
> org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.executeQuery(JdbcRequestHandler.java:456)
> at
> org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.handle(JdbcRequestHandler.java:203)
> at
> org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:160)
> at
> org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:44)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterChain$TailFilter.onMessageReceived(GridNioFilterChain.java:279)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
> at
> org.apache.ignite.internal.util.nio.GridNioAsyncNotifyFilter$3.body(GridNioAsyncNotifyFilter.java:97)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at
> org.apache.ignite.internal.util.worker.GridWorkerPool$1.run(GridWorkerPool.java:70)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: class org.apache.ignite.IgniteCheckedException:
> org.h2.table.TableView cannot be cast to
> org.apache.ignite.internal.processors.query.h2.opt.GridH2Table
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2601)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2044)
> ... 12 more
> Caused by: java.lang.ClassCastException: org.h2.table.TableView cannot be
> cast to org.apache.ignite.internal.processors.query.h2.opt.GridH2Table
> at
> org.apache.ignite.internal.processors.query.h2.sql.GridSqlQuerySplitter.extractPartitionFromEquality(GridSqlQuerySplitter.java:2336)
> at
> org.apache.ignite.internal.processors.query.h2.sql.GridSqlQuerySplitter.extractPartition(GridSqlQuerySplitter.java:2268)
> at
> org.apache.ignite.internal.processors.query.h2.sql.GridSqlQuerySplitter.derivePartitionsFromQuery(GridSqlQuerySplitter.java:2250)
> at
> org.apache.ignite.internal.processors.query.h2.sql.GridSqlQuerySplitter.splitSelect(GridSqlQuerySplitter.java:1539)
> at
> org.apache.ignite.internal.processors.query.h2.sql.GridSqlQuerySplitter.splitQueryModel(GridSqlQuerySplitter.java:1227)
> at
>
[jira] [Updated] (IGNITE-9321) MVCC: support cache events
[
https://issues.apache.org/jira/browse/IGNITE-9321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Pavlukhin updated IGNITE-9321:
---
Description:
Currently cache events are not fired for MVCC caches. Need to restore all cache
events.
Starting point: {{org.apache.ignite.events.EventType#EVTS_CACHE}}. All these
events should work in the same way on both MVCC and non-MVCC caches.
Events are supposed to fire right away without deferring to transaction end
phase.
was:
Currently cache events are not fired for MVCC caches. Need to restore all cache
events.
Starting point: \{{org.apache.ignite.events.EventType#EVTS_CACHE}}. All these
events should work in the same way on both MVCC and non-MVCC caches.
> MVCC: support cache events
> --
>
> Key: IGNITE-9321
> URL: https://issues.apache.org/jira/browse/IGNITE-9321
> Project: Ignite
> Issue Type: Task
> Components: mvcc
>Reporter: Vladimir Ozerov
>Assignee: Ivan Pavlukhin
>Priority: Major
> Fix For: 2.7
>
>
> Currently cache events are not fired for MVCC caches. Need to restore all
> cache events.
> Starting point: {{org.apache.ignite.events.EventType#EVTS_CACHE}}. All these
> events should work in the same way on both MVCC and non-MVCC caches.
> Events are supposed to fire right away without deferring to transaction end
> phase.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7777) Thin Client lib: Node.js
[ https://issues.apache.org/jira/browse/IGNITE-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617520#comment-16617520 ] Alexey Kosenchuk commented on IGNITE-: -- For historical purpose - all original readmes and instructions are summarized here https://github.com/nobitlost/ignite/blob/ignite--docs/modules/platforms/nodejs/README.md > Thin Client lib: Node.js > > > Key: IGNITE- > URL: https://issues.apache.org/jira/browse/IGNITE- > Project: Ignite > Issue Type: New Feature > Components: thin client >Reporter: Alexey Kosenchuk >Assignee: Alexey Kosenchuk >Priority: Major > Fix For: 2.7 > > > Implement Thin (lightweight) Client lib in Node.js programming language for > Ignite Binary Client Protocol. > Examples of other Thin Clients: > .net > https://github.com/apache/ignite/tree/master/modules/platforms/dotnet/Apache.Ignite.Core/Impl/Client > java https://github.com/gridgain/apache-ignite/tree/ignite-7421 > https://apacheignite.readme.io/v2.3/docs/java-thin-client > Scope of work > - > Functionality: > Support all operations of the Ignite Binary Client Protocol 2.4: > https://apacheignite.readme.io/v2.4/docs/binary-client-protocol > Except: > OP_QUERY_SCAN (requires changes on the server side) > OP_REGISTER_BINARY_TYPE_NAME, OP_GET_BINARY_TYPE_NAME (not applicable) > Support name/password authentication (not in the protocol yet). > Support optional SSL/TLS communication. > Support failover/reconnect algorithm: > https://issues.apache.org/jira/browse/IGNITE-7282 > http://apache-ignite-developers.2346864.n4.nabble.com/Thin-client-failover-mechanism-ODBC-JDBC-td26553.html > Minimal Node.js version - 8.0 > Promise asynch/await to be used. > Examples: > Cover all basic features - Key-value API, SQL queries, Cluster > configuration/management, Authentication, SSL/TLS. > Tests: > Jasmine tests for all API methods and all basic features. > Simple Jasmine tests to start examples. > The tests should call external commands/scripts to start/stop the nodes. > Docs: > Auto-generated API spec from jsdoc comments: > http://usejsdoc.org/ > https://www.npmjs.com/package/jsdoc > Readme for the lib. > Simple instruction to setup/run examples. > Simple instruction to setup/run Jasmine tests. > Docs should be on readme.io or in github - TBD > Released as NPM module on https://www.npmjs.com > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-5732) Provide API to test compatibility with old releases
[
https://issues.apache.org/jira/browse/IGNITE-5732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov reassigned IGNITE-5732:
Assignee: Vyacheslav Daradur (was: Dmitriy Pavlov)
> Provide API to test compatibility with old releases
> ---
>
> Key: IGNITE-5732
> URL: https://issues.apache.org/jira/browse/IGNITE-5732
> Project: Ignite
> Issue Type: New Feature
>Affects Versions: 2.1
>Reporter: Vyacheslav Daradur
>Assignee: Vyacheslav Daradur
>Priority: Major
> Fix For: 2.3
>
>
> Need to provide an opportunity to test compatibility with old releases.
> The main idea is the method {code}startGrid(ver){code} in the testing
> framework, which would start an instance via downloaded "jar" from the Maven
> repo.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9617) Different input possibilities for services page
[ https://issues.apache.org/jira/browse/IGNITE-9617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617501#comment-16617501 ] ASF GitHub Bot commented on IGNITE-9617: SomeFire opened a new pull request #11: IGNITE-9617 Different input possibilities for services page URL: https://github.com/apache/ignite-teamcity-bot/pull/11 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Different input possibilities for services page > --- > > Key: IGNITE-9617 > URL: https://issues.apache.org/jira/browse/IGNITE-9617 > Project: Ignite > Issue Type: Sub-task >Reporter: Ryabov Dmitrii >Assignee: Ryabov Dmitrii >Priority: Minor > > We should improve usability. Currently branch field requieres full TeamCity > branch name like on index page. It should accept PR number too. > Same about JIRA ticket field. It should accept "IGNITE-XXX" and number only. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9617) Different input possibilities for services page
Ryabov Dmitrii created IGNITE-9617: -- Summary: Different input possibilities for services page Key: IGNITE-9617 URL: https://issues.apache.org/jira/browse/IGNITE-9617 Project: Ignite Issue Type: Sub-task Reporter: Ryabov Dmitrii Assignee: Ryabov Dmitrii We should improve usability. Currently branch field requieres full TeamCity branch name like on index page. It should accept PR number too. Same about JIRA ticket field. It should accept "IGNITE-XXX" and number only. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9532) Binary mode for Ignite Queue
[
https://issues.apache.org/jira/browse/IGNITE-9532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617490#comment-16617490
]
Anton Vinogradov commented on IGNITE-9532:
--
[~uday]
It looks like it should be successful.
Please debug why comparison returns {{false}}.
It will be easy to answer should it be successful or not once we find the
reason.
> Binary mode for Ignite Queue
>
>
> Key: IGNITE-9532
> URL: https://issues.apache.org/jira/browse/IGNITE-9532
> Project: Ignite
> Issue Type: New Feature
> Components: binary, data structures
>Reporter: Uday Kale
>Assignee: Uday Kale
>Priority: Major
> Fix For: 2.8
>
>
> Add binary mode (withKeepBinary) to Data Structures Queue.
> This will allow retrieving values in binary format when needed or when class
> is not available, and will allow implementing the structures in other
> platforms (.NET, C++).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9321) MVCC: support cache events
[
https://issues.apache.org/jira/browse/IGNITE-9321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-9321:
Description:
Currently cache events are not fired for MVCC caches. Need to restore all cache
events.
Starting point: \{{org.apache.ignite.events.EventType#EVTS_CACHE}}. All these
events should work in the same way on both MVCC and non-MVCC caches.
was:Currently cache events are not fired for MVCC caches. Need to restore all
cache events.
> MVCC: support cache events
> --
>
> Key: IGNITE-9321
> URL: https://issues.apache.org/jira/browse/IGNITE-9321
> Project: Ignite
> Issue Type: Task
> Components: mvcc
>Reporter: Vladimir Ozerov
>Assignee: Ivan Pavlukhin
>Priority: Major
> Fix For: 2.7
>
>
> Currently cache events are not fired for MVCC caches. Need to restore all
> cache events.
> Starting point: \{{org.apache.ignite.events.EventType#EVTS_CACHE}}. All these
> events should work in the same way on both MVCC and non-MVCC caches.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-7793) SQL does not work if value has sql field which name equals to affinity key name
[
https://issues.apache.org/jira/browse/IGNITE-7793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Pudov updated IGNITE-7793:
Summary: SQL does not work if value has sql field which name equals to
affinity key name (was: SQL does not work if value has index field which name
equals to affinity key name)
> SQL does not work if value has sql field which name equals to affinity key
> name
> ---
>
> Key: IGNITE-7793
> URL: https://issues.apache.org/jira/browse/IGNITE-7793
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.3
>Reporter: Mikhail Cherkasov
>Assignee: Maxim Pudov
>Priority: Blocker
> Fix For: 2.7
>
>
> SQL does not work if value has index filed which name equals to affinity key
> name:
> {code:java}
> public class AKey {
> @AffinityKeyMapped
> int a;
> public AKey(int a) {
> this.a = a;
> }
> }
> public class AVal {
> @QuerySqlField
> int a;
> public AVal(int a) {
> this.a = a;
> }
> }
> AKey aKey = new AKey(1);
> AVal aVal = new AVal(0);
> IgniteCache cache = ignite.cache("Instrument");
> cache.put(aKey, aVal);
> SqlFieldsQuery query = new SqlFieldsQuery("select * from \"Instrument\".AVal
> it where it.a=?");
> List> res = cache.query(query.setArgs(0)).getAll();
> if(res.isEmpty()) {
> System.out.println("! FAILED !!!");
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-9321) MVCC: support cache events
[ https://issues.apache.org/jira/browse/IGNITE-9321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov reassigned IGNITE-9321: --- Assignee: Ivan Pavlukhin (was: Vladimir Ozerov) > MVCC: support cache events > -- > > Key: IGNITE-9321 > URL: https://issues.apache.org/jira/browse/IGNITE-9321 > Project: Ignite > Issue Type: Task > Components: mvcc >Reporter: Vladimir Ozerov >Assignee: Ivan Pavlukhin >Priority: Major > Fix For: 2.7 > > > Currently cache events are not fired for MVCC caches. Need to restore all > cache events. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-9532) Binary mode for Ignite Queue
[ https://issues.apache.org/jira/browse/IGNITE-9532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617470#comment-16617470 ] Uday Kale edited comment on IGNITE-9532 at 9/17/18 12:57 PM: - [~avinogradov], The asserts in your code snippets are working. Do you want me to debug your snippet or mine? In case I wasn't clear, I just want to know whether the unit test I shared should succeed or not. was (Author: uday): [~avinogradov], The asserts in your code snippets are working. Do you want me to debug your snippet or mine? > Binary mode for Ignite Queue > > > Key: IGNITE-9532 > URL: https://issues.apache.org/jira/browse/IGNITE-9532 > Project: Ignite > Issue Type: New Feature > Components: binary, data structures >Reporter: Uday Kale >Assignee: Uday Kale >Priority: Major > Fix For: 2.8 > > > Add binary mode (withKeepBinary) to Data Structures Queue. > This will allow retrieving values in binary format when needed or when class > is not available, and will allow implementing the structures in other > platforms (.NET, C++). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9321) MVCC: support cache events
[ https://issues.apache.org/jira/browse/IGNITE-9321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov reassigned IGNITE-9321: --- Assignee: Vladimir Ozerov > MVCC: support cache events > -- > > Key: IGNITE-9321 > URL: https://issues.apache.org/jira/browse/IGNITE-9321 > Project: Ignite > Issue Type: Task > Components: mvcc >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Major > Fix For: 2.7 > > > Currently cache events are not fired for MVCC caches. Need to restore all > cache events. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9321) MVCC: support cache events
[ https://issues.apache.org/jira/browse/IGNITE-9321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-9321: Description: Currently cache events are not fired for MVCC caches. Need to restore all cache events. (was: Currently cache events are not fired for MVCC caches. Need to decide what to do with it. Possible options: # Fix events (will require separate data structure and incur possibly serious overhead) # Do not fire events at all # Introduce new events which will not require additional data structures (e.g. "entry_changed" which may be fired even if transaction is rolled back in the end)) > MVCC: support cache events > -- > > Key: IGNITE-9321 > URL: https://issues.apache.org/jira/browse/IGNITE-9321 > Project: Ignite > Issue Type: Task > Components: mvcc >Reporter: Vladimir Ozerov >Priority: Major > Fix For: 2.7 > > > Currently cache events are not fired for MVCC caches. Need to restore all > cache events. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9538) MVCC TX: Send partition update counters to backup nodes on prepare state.
[ https://issues.apache.org/jira/browse/IGNITE-9538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov reassigned IGNITE-9538: --- Assignee: Roman Kondakov (was: Ivan Pavlukhin) > MVCC TX: Send partition update counters to backup nodes on prepare state. > - > > Key: IGNITE-9538 > URL: https://issues.apache.org/jira/browse/IGNITE-9538 > Project: Ignite > Issue Type: Task > Components: cache, mvcc >Reporter: Igor Seliverstov >Assignee: Roman Kondakov >Priority: Major > Fix For: 2.7 > > > There are several issues with partition update counters consistency in > transactional caches. The next approach solves most of them: > # Count per-partition updates > # on prepare state on primary node update current partition counter > incrementing it by per-partition updates count and send initial value with > updates count to backup nodes > # on backup nodes hold all pending updates and update partition update > counter applying the lowest gapless update (on tx finish). > # on historical rebalance use partition update counter as start point. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9532) Binary mode for Ignite Queue
[ https://issues.apache.org/jira/browse/IGNITE-9532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617470#comment-16617470 ] Uday Kale commented on IGNITE-9532: --- [~avinogradov], The asserts in your code snippets are working. Do you want me to debug your snippet or mine? > Binary mode for Ignite Queue > > > Key: IGNITE-9532 > URL: https://issues.apache.org/jira/browse/IGNITE-9532 > Project: Ignite > Issue Type: New Feature > Components: binary, data structures >Reporter: Uday Kale >Assignee: Uday Kale >Priority: Major > Fix For: 2.8 > > > Add binary mode (withKeepBinary) to Data Structures Queue. > This will allow retrieving values in binary format when needed or when class > is not available, and will allow implementing the structures in other > platforms (.NET, C++). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-9588) Separate page for JIRA, GitHub actions
[ https://issues.apache.org/jira/browse/IGNITE-9588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryabov Dmitrii resolved IGNITE-9588. Resolution: Done > Separate page for JIRA, GitHub actions > -- > > Key: IGNITE-9588 > URL: https://issues.apache.org/jira/browse/IGNITE-9588 > Project: Ignite > Issue Type: Sub-task >Reporter: Ryabov Dmitrii >Assignee: Ryabov Dmitrii >Priority: Major > > To separate JIRA and GitHub actions from other action on index page we need > to create an additional page, opened by tab on the panel with Home and > Compare Builds. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9532) Binary mode for Ignite Queue
[
https://issues.apache.org/jira/browse/IGNITE-9532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617456#comment-16617456
]
Anton Vinogradov commented on IGNITE-9532:
--
[~uday]
Please make sure that
{noformat}
SameHashItem a = new SameHashItem(Integer.toString(14)));
SameHashItem b = new SameHashItem(Integer.toString(14)));
assert a.hashCode() == b.hashCode();
assert a.equals(b);
{noformat}
In case asserts are ok, just debug comparison and let me know the reason,
please.
> Binary mode for Ignite Queue
>
>
> Key: IGNITE-9532
> URL: https://issues.apache.org/jira/browse/IGNITE-9532
> Project: Ignite
> Issue Type: New Feature
> Components: binary, data structures
>Reporter: Uday Kale
>Assignee: Uday Kale
>Priority: Major
> Fix For: 2.8
>
>
> Add binary mode (withKeepBinary) to Data Structures Queue.
> This will allow retrieving values in binary format when needed or when class
> is not available, and will allow implementing the structures in other
> platforms (.NET, C++).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9616) SQL: Introduce H2 factory for holder of aggregate result
[
https://issues.apache.org/jira/browse/IGNITE-9616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-9616:
-
Description:
H2 collects aggregate results at the simple HashMap (groups set and values set).
This causes an OOME error on large groups set and large group size with
{{DISTINCT}}.
We have to introduce way to use our own implementation of the aggregate
result's container.
H2 issue:
[#1433|https://github.com/h2database/h2database/issues/1433#issuecomment-421045128]
was:
H2 collects aggregate results at the simple HashMap (groups set and values set).
This causes an OOME error on large groups set and large group size with
{{DISTINCT}}.
We have to introduce way to use our own implementation of the aggregate
result's container.
> SQL: Introduce H2 factory for holder of aggregate result
>
>
> Key: IGNITE-9616
> URL: https://issues.apache.org/jira/browse/IGNITE-9616
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Affects Versions: 2.6
>Reporter: Taras Ledkov
>Priority: Major
>
> H2 collects aggregate results at the simple HashMap (groups set and values
> set).
> This causes an OOME error on large groups set and large group size with
> {{DISTINCT}}.
> We have to introduce way to use our own implementation of the aggregate
> result's container.
> H2 issue:
> [#1433|https://github.com/h2database/h2database/issues/1433#issuecomment-421045128]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9616) SQL: Introduce H2 factory for holder of aggregate result
Taras Ledkov created IGNITE-9616:
Summary: SQL: Introduce H2 factory for holder of aggregate result
Key: IGNITE-9616
URL: https://issues.apache.org/jira/browse/IGNITE-9616
Project: Ignite
Issue Type: Improvement
Components: sql
Affects Versions: 2.6
Reporter: Taras Ledkov
H2 collects aggregate results at the simple HashMap (groups set and values set).
This causes an OOME error on large groups set and large group size with
{{DISTINCT}}.
We have to introduce way to use our own implementation of the aggregate
result's container.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-7793) SQL does not work if value has index field which name equals to affinity key name
[
https://issues.apache.org/jira/browse/IGNITE-7793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Pudov updated IGNITE-7793:
Summary: SQL does not work if value has index field which name equals to
affinity key name (was: SQL does not work if value has index filed which name
equals to affinity key name)
> SQL does not work if value has index field which name equals to affinity key
> name
> -
>
> Key: IGNITE-7793
> URL: https://issues.apache.org/jira/browse/IGNITE-7793
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.3
>Reporter: Mikhail Cherkasov
>Assignee: Maxim Pudov
>Priority: Blocker
> Fix For: 2.7
>
>
> SQL does not work if value has index filed which name equals to affinity key
> name:
> {code:java}
> public class AKey {
> @AffinityKeyMapped
> int a;
> public AKey(int a) {
> this.a = a;
> }
> }
> public class AVal {
> @QuerySqlField
> int a;
> public AVal(int a) {
> this.a = a;
> }
> }
> AKey aKey = new AKey(1);
> AVal aVal = new AVal(0);
> IgniteCache cache = ignite.cache("Instrument");
> cache.put(aKey, aVal);
> SqlFieldsQuery query = new SqlFieldsQuery("select * from \"Instrument\".AVal
> it where it.a=?");
> List> res = cache.query(query.setArgs(0)).getAll();
> if(res.isEmpty()) {
> System.out.println("! FAILED !!!");
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-4188) Savepoints support inside of Ignite Transactions
[
https://issues.apache.org/jira/browse/IGNITE-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617438#comment-16617438
]
Ryabov Dmitrii commented on IGNITE-4188:
{panel:title=Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Binary Objects (Simple Mapper Basic){color} [[tests 0 TIMEOUT ,
Exit Code |https://ci.ignite.apache.org/viewLog.html?buildId=1850179]]
* TxSavepointsTransactionalCacheTest.testPutWithExplicitTx (last started)
{color:#d04437}Basic 1{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=1850276]]
* TxSavepointsTransactionalCacheTest.testPutWithExplicitTx (last started)
{color:#d04437}Cache (Restarts) 1{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=1850256]]
*
GridCacheReplicatedNodeRestartSelfTest.testRestartWithTxPutAllFourNodesTwoBackups
(last started)
{color:#d04437}Queries 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=1850265]]
* IgniteBinaryCacheQueryTestSuite:
IndexingCachePartitionLossPolicySelfTest.testReadWriteSafeWithBackupsAfterKillCrd
- 0,0% fails in last 100 master runs.
{color:#d04437}SPI{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=1850215]]
* IgniteSpiTestSuite: TcpCommunicationSpiDropNodesTest.testOneNode - 0,0% fails
in last 100 master runs.
{color:#d04437}PDS 2{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=1850239]]
* IgnitePdsTestSuite2:
IgnitePdsPartitionFilesDestroyTest.testPartitionFileDestroyCrashRecovery1 -
0,0% fails in last 100 master runs.
{color:#d04437}PDS (Direct IO) 2{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=1850235]]
* IgnitePdsNativeIoTestSuite2:
IgniteWalFormatFileFailoverTest.testFailureHandlerTriggered - 0,0% fails in
last 100 master runs.
{color:#d04437}Cache 5{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=1850263]]
* IgniteCacheWithIndexingTestSuite:
CacheTtlAtomicPartitionedSelfTest.testDefaultTimeToLiveLoadAll - 0,0% fails in
last 100 master runs.
{color:#d04437}Continuous Query 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=1850189]]
* IgniteCacheQuerySelfTestSuite3:
CacheContinuousWithTransformerPartitionedSelfTest.testContinuousWithTransformerAndRegularListenerAsync
- 0,0% fails in last 100 master runs.
{color:#d04437}Compute (Grid){color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=1850187]]
* IgniteBinaryObjectsComputeGridTestSuite:
GridMultithreadedJobStealingSelfTest.testJoinedNodeCanStealJobs - 0,0% fails in
last 100 master runs.
{color:#d04437}Java Client{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=1850201]]
* IgniteClientTestSuite: ClientReconnectionSelfTest.testFailedInit - 0,0% fails
in last 100 master runs.
{panel}
[TeamCity Run
All|http://ci.ignite.apache.org/viewLog.html?buildId=1850279buildTypeId=IgniteTests24Java8_RunAll]
> Savepoints support inside of Ignite Transactions
>
>
> Key: IGNITE-4188
> URL: https://issues.apache.org/jira/browse/IGNITE-4188
> Project: Ignite
> Issue Type: Task
>Reporter: Denis Magda
>Assignee: Ryabov Dmitrii
>Priority: Major
> Fix For: 2.7
>
>
> A savepoint is a special mark inside a transaction that allows all commands
> that are executed after it was established to be rolled back, restoring the
> transaction state to what it was at the time of the savepoint.
> Here is a reference to the similar functionality implemented by some of RDBMs
> vendors.
> https://www.postgresql.org/docs/8.1/static/sql-savepoint.html
> https://docs.oracle.com/cd/B19306_01/server.102/b14200/statements_10001.htm
> http://dev.mysql.com/doc/refman/5.7/en/savepoint.html
> Consider the following example.
> {code}
> BEGIN;
> INSERT INTO table1 VALUES (1);
> SAVEPOINT my_savepoint;
> INSERT INTO table1 VALUES (2);
> ROLLBACK TO SAVEPOINT my_savepoint;
> INSERT INTO table1 VALUES (3);
> COMMIT;
> {code}
> The execution result must guarantee that only values 1 and 3 are inserted
> into table1.
> In Ignite, it should be supported this way (preserving the same behavior as
> above).
> {code}
> Ignite ignite = ;
> IgniteCache c = ;
> try (Transaction tx = ignite.transactions().txStart()) {
> c.put(1, 1);
>
> tx.savepoint("mysavepoint");
>
> c.put(2, 2);
>
> tx.rollbackToSavepoint("mysavepoint");
>
> c.put(3, 3);
>
> tx.commit();
> }
> {code}
> As a summary the following has to be supported on Ignite side:
> - The {{savepoint}} method which will set a named transaction savepoint with
> a name of an identifier.
> - Multiple savepoints defined within a transaction. The names of the
> savepoints have to differ from
[jira] [Commented] (IGNITE-9465) Node.js client: improve complex object flags processing
[ https://issues.apache.org/jira/browse/IGNITE-9465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16617435#comment-16617435 ] Igor Sapego commented on IGNITE-9465: - [~ekaterina.vergizova], looks good. I'm going to merge it to master now. Do we need to edit any documentation on readme.io? If yes - create separate ticket for it. > Node.js client: improve complex object flags processing > --- > > Key: IGNITE-9465 > URL: https://issues.apache.org/jira/browse/IGNITE-9465 > Project: Ignite > Issue Type: Improvement > Components: thin client >Reporter: Alexey Kosenchuk >Assignee: ekaterina.vergizova >Priority: Major > Fix For: 2.7 > > > 1) fix the issue in the full schema support > 2) do not throw exception when object with HAS_RAW_DATA flag is received > 3) support OFFSET_*_BYTE flags/optimizations when writing data -- This message was sent by Atlassian JIRA (v7.6.3#76005)
