Prachi,
This line in your message
> Requirement already satisfied: pyignite in
> ./Downloads/ignite-python/modules/platforms/python (0.3.1)
looks like you already did an installation of pyignite in this
environment before (maybe with "pip install -e ")
from 'Downloads' folder, then delete or
Hi Andrew,
I have updated the tests and also added java docs.
Can you please review and share feedback.
Regards
Saikat
On Sun, Sep 16, 2018 at 11:53 AM, Saikat Maitra
wrote:
> Hi Andrew,
>
> I have updated the tests and also added java docs.
>
> Please review and share feedback.
>
> Regar
Hello, Igniters.
Is there any specific reason why this ticket is removed from 2.7 scope?
I think this ticket is important for both usability and performance.
Without this ticket, we have to create an index manually identical to
primary key if we want to use SQL query.
https://issues.apache.org/ji
Hello,
I have an EntryProcessor that is running inside an
ignite.compute().call(callable) from a client node.
The 3 servers are using peer class loading and do not have any of these
custom classes on its path.
FragmentAssignToScannerEntryProcessor class:
import java.io.Serializable;
import javax
GitHub user slukyano opened a pull request:
https://github.com/apache/ignite/pull/4793
IGNITE-9646: Added jackson dependencies back to ignite-aws.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9646
Hi Dmitry,
I tried to follow the instructions for the Python thin client installation
[1].
~$ pip install pyignite
Requirement already satisfied: pyignite in
./Downloads/ignite-python/modules/platforms/python (0.3.1)
Requirement already satisfied: typing==3.6.4 in
/Library/Frameworks/Python.frame
Val can be the final reviewer. He knows this component pretty well.
Val, could you help the guys with this?
--
Denis
On Wed, Sep 19, 2018 at 3:14 AM Anton Vinogradov wrote:
> Nikolay,
>
> I'll perform prereview once PR will be ready.
> Then we'll need some time to fix all found issues.
> After
Hi Igniters!
I've filled an umbrella ticket [1] to track all tickets which will be
implemented in phase 1.
We reworked internals completely that allow us to provide us with
several main features:
* synchronous deployment
* propagation of deployment errors across the cluster
* basic deployment fail
Stanislav Lukyanov created IGNITE-9651:
--
Summary: Binary objects comparison may fail when the same
reference occurs more than once
Key: IGNITE-9651
URL: https://issues.apache.org/jira/browse/IGNITE-9651
Hi Dmitriy Ryabov,
could you please create and share INFRA ticket to disable comment
forwarding to the dev list?
Sincerely,
Dmitriy Pavlov
ср, 19 сент. 2018 г. в 19:02, GitBox :
> SomeFire commented on a change in pull request #14: Performance
> URL:
> https://github.com/apache/ignite-teamcity-
Dmitriy Ryabov,
Thank you for your comments to PR14. Merged. Could you please take a look
at the proposed changes?
Idea is that for hot method getBuildHistory we can limit the number of
builds to be loaded from TC REST.
Sincerely,
Dmitriy Pavlov
ср, 19 сент. 2018 г. в 20:43, GitBox :
> dspavlo
dspavlov opened a new pull request #15: Incremental build upload
URL: https://github.com/apache/ignite-teamcity-bot/pull/15
This is an automated message from the Apache Git Service.
To respond to the message, please log on Gi
asfgit closed pull request #14: Performance
URL: https://github.com/apache/ignite-teamcity-bot/pull/14
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL
asfgit closed pull request #13: Green table header for PRs without possible
blockers
URL: https://github.com/apache/ignite-teamcity-bot/pull/13
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 t
Hello!
Why don't you use CacheKeyConfiguration as mentioned in the ticket?
Regards,
--
Ilya Kasnacheev
ср, 19 сент. 2018 г. в 5:55, kcheng.mvp :
> I checked the source code just now and found *AffinityKey* is using
> *@AffinityKeyMapped*
> that's to say *AffinityKey* has the same issue.
> am
Ilya Kasnacheev created IGNITE-9650:
---
Summary: java.math.BigDecimal / .Net decimal columns shown as
OTHER in JDBC Thin metadata
Key: IGNITE-9650
URL: https://issues.apache.org/jira/browse/IGNITE-9650
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4739
---
SomeFire commented on a change in pull request #14: Performance
URL: https://github.com/apache/ignite-teamcity-bot/pull/14#discussion_r218864819
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/web/rest/pr/GetPrTestFailures.java
##
@@ -130,17 +133,19 @
SomeFire commented on a change in pull request #14: Performance
URL: https://github.com/apache/ignite-teamcity-bot/pull/14#discussion_r218863247
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/TcHelper.java
##
@@ -188,7 +183,8 @@ private BranchesTrack
SomeFire commented on a change in pull request #14: Performance
URL: https://github.com/apache/ignite-teamcity-bot/pull/14#discussion_r218862350
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/BuildChainProcessor.java
##
@@ -101,47 +109,24 @@
SomeFire commented on a change in pull request #14: Performance
URL: https://github.com/apache/ignite-teamcity-bot/pull/14#discussion_r218863424
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/issue/IssueDetector.java
##
@@ -386,15 +386,17 @@ private
SomeFire commented on a change in pull request #14: Performance
URL: https://github.com/apache/ignite-teamcity-bot/pull/14#discussion_r218862428
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/BuildChainProcessor.java
##
@@ -101,47 +109,24 @@
SomeFire commented on a change in pull request #14: Performance
URL: https://github.com/apache/ignite-teamcity-bot/pull/14#discussion_r218863573
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/util/ExceptionUtil.java
##
@@ -30,6 +30,9 @@
* @para
SomeFire commented on a change in pull request #14: Performance
URL: https://github.com/apache/ignite-teamcity-bot/pull/14#discussion_r218864501
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/BuildChainProcessor.java
##
@@ -56,23 +59,25 @@
* @p
dspavlov opened a new pull request #14: Performance
URL: https://github.com/apache/ignite-teamcity-bot/pull/14
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use
Pavel Kovalenko created IGNITE-9649:
---
Summary: Rework logging in important places
Key: IGNITE-9649
URL: https://issues.apache.org/jira/browse/IGNITE-9649
Project: Ignite
Issue Type: Improve
Github user oignatenko closed the pull request at:
https://github.com/apache/ignite/pull/4774
---
Dmitriy Pavlov created IGNITE-9648:
--
Summary: Improve doc and javadoc for Ignite distrubuted lock
Key: IGNITE-9648
URL: https://issues.apache.org/jira/browse/IGNITE-9648
Project: Ignite
Issu
Hi Dmitrii,
thank you for making an additional announce.
And I appreciate your efforts to make this contribution happen.
During Bot existence it was always developed based on Igniters feedback,
so, as always, your feedback is very welcome.
Sincerely,
Dmitriy Pavlov
ср, 19 сент. 2018 г. в 15
GitHub user alamar opened a pull request:
https://github.com/apache/ignite/pull/4792
Ignite 2.5 master
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2.5-master
Alternatively you can review and app
I've been working on https://issues.apache.org/jira/browse/IGNITE-7793
and found out that we don't have validation for such case:
PersonKey {
int id;
String name;
}
Person {
String name;
}
CacheKeyConfiguration keyCfg =new CacheKeyConfiguration(PersonKey.getName(),
"name");
QueryEnt
Nikolay,
since we talk about scope freeze all you need now just create
ignite-2.7 branch. We still can have tickets targeted to 2.7 release
in progress. So you shouldn't move tickets to 2.8 because they can be
targeted to 2.7 intentionally and will be merged to master and
ignite-2.7 branches.
On W
Ivan Pavlukhin created IGNITE-9647:
--
Summary: EVT_CACHE_OBJECT_REMOVED is fired when entry is absent
before remove
Key: IGNITE-9647
URL: https://issues.apache.org/jira/browse/IGNITE-9647
Project: Ign
Hello, Igniters!
If you din't saw the "Apache Ignite TeamCity Bot: Features overview"
webinar, you should know:
Ignite TC Bot can detect failures appeared in the Pull Request and comment
JIRA ticket with this failures.
If PR has no new failures - bot will comment about the absence of such
failure
GitHub user junphine opened a pull request:
https://github.com/apache/ignite/pull/4791
support for config fulltext index in queryEntities
Ilya Kasnacheev created IGNITE-9646:
---
Summary: CLONE - Regression in release build for ignite-zookeeper
module
Key: IGNITE-9646
URL: https://issues.apache.org/jira/browse/IGNITE-9646
Project: Ignite
PetrovMikhail created IGNITE-9645:
-
Summary: Add comparison of failed tests lists in two date intervals
Key: IGNITE-9645
URL: https://issues.apache.org/jira/browse/IGNITE-9645
Project: Ignite
Hi Igniters,
Who could advise about possible reasons? Spring data version was updated
recently, but examples tests seem to be passing.
If it is not a local problem then I consider this ticket is a blocker of
2.7.
Sincerely,
Dmitriy Pavlov
ср, 19 сент. 2018 г. в 11:44, Stepan Pilschikov (JIRA) :
Sergey Grimstad created IGNITE-9644:
---
Summary: SQL: local DML query should pin affected partitions
Key: IGNITE-9644
URL: https://issues.apache.org/jira/browse/IGNITE-9644
Project: Ignite
Is
Hi Dmitriy,
Probably we can standalone page for the Bot description because the Bot
became standalone module not too much related to MTCGA.
If you would like to contribute some description please share your wiki
username, I will grant necessary permission.
Sincerely,
Dmitriy Pavlov
ср, 19 сент.
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4790
---
Nikolay,
I'll perform prereview once PR will be ready.
Then we'll need some time to fix all found issues.
After that final review by another expert will be required.
Let's define the deadline for final PR and reviewer (Alexey Goncharuk?).
In other words, let's define the exact date until which fi
Ryabov Dmitrii created IGNITE-9643:
--
Summary: [TC Bot] update cwiki
Key: IGNITE-9643
URL: https://issues.apache.org/jira/browse/IGNITE-9643
Project: Ignite
Issue Type: Task
Repor
Hello, Igniters.
Currently, we are working on release scope for Apache Ignite 2.7
We had plans to include "Service Grid Redesign. Phase 1" to 2.7 release.
If I understand correctly, the plan is following - We should have PR that
is ready for review at the end of September.
This deadline is very
Hello, Igniters.
Vova, thank you for pointing this out.
I ask all community members to iterate over assigned tickets.
Please, move your tickets to 2.8 release if work is still in progress.
At the end of the day, I will do it by myself and tomorrow we should have
release scope prepared.
ср, 19 с
Alexei,
> Summing up, I suggest adding new public
method IgniteCache.preloadPartition(partId).
If I understand correctly use case, the user wants to retrieve whole data
from
the cache (not only single partition) having slow HDD. So, my suggestion is
to
create methods of public API like these:
`p
My point was not about code freeze, but about scope freeze, what means that
starting from this point AI 2.7 release should not receive any commits
which doesn't relate to it.
On Wed, Sep 19, 2018 at 11:55 AM Anton Vinogradov wrote:
> Vova,
>
> AFAIK, codefreeze was not announced yet.
> Correct m
Vova,
AFAIK, codefreeze was not announced yet.
Correct me in case I missed this.
Now, Nikolay finishing checks that he's able to perform release (everything
installed and properly configured).
So, I recommend him to mention this check here to solve any
misunderstanding in case some branches or ta
Anton,
What do you mean under "preparation to real 2.7". It is already real, we
reached formal code freeze phase we agreed on. At this point we need to
exclude non-2.7 commits, otherwise we will not be able to come to stable
branch in two weeks.
For this reason creating a branch for 2.7 at the mom
Stepan Pilschikov created IGNITE-9642:
-
Summary: Examples: can't compile springdata examples
Key: IGNITE-9642
URL: https://issues.apache.org/jira/browse/IGNITE-9642
Project: Ignite
Issue
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4780
---
Hi
I brought ignite server on k8s cluster.
Set the below property for a cache i wanted to check the metrics
Then i started the client and tried to push the data into ignite cache.
I am able to see the data in the cache.
But the values for the following metrics i am getting as 0. Can some one le
52 matches
Mail list logo
