Dmitriy, Pavel,
Everything that gets accepted into the project has to make sense. I agree
with Vladimir - we do not need more than one file system in Ignite. Given
the number of usage and questions we get about IGFS, I would question
whether Ignite needs a file system at all.
As community members
I vote to remove the fabric from the build in the easiest way possible. Can
other Igniters comment?
D.
On Wed, Aug 1, 2018 at 12:46 PM, Petr Ivanov wrote:
> My concern here is exactly about internal build processes — removing
> fabric from the name of binary archive (with any way) will break lo
Hi Yakov,
Currently TC agents defended by Docker virtual network, that's why we don't
see intersection between several clusters, but in case of any step aside
(running several suites on one agent, running several tests on one machine
and so on) we will have problems and return back to this convers
Hello Alexey,
It's not so difficult to implement new type of indexing of data, but if you
want to reach performance in distributed environment you need to have
strong knowledge of a data you're indexing and what kind of queries you
want to execute.
Should be this index in-memory only or you want t
It should be true, otherwise we would have nodes from all agents
intersecting. No?
And multicast IP finder is the defailt one, so I would not reduce its test
volume.
Yakov Zhdanov
www.gridgain.com
2018-08-02 0:32 GMT+03:00 Dmitriy Pavlov :
> Hi Yakov,
>
> Regarding Each TC agent use own multica
Hi Yakov,
Regarding Each TC agent use own multicast: I'm not sure it is true, TC
admins tried to do so, but not succeded.
One more reason is speed of tests run. Why do we need to scan something if
we always will connect localhost. TC tests do not use multicast in almost
every test.
Sincerely,
Dm
I disagree. Probably, no change required. Each TC agent use own multicast
group so nodes do not intersect. If any of the test does not properly clean
up and leaves nodes running this dhould be flagged as test fail which is
the case.
Please provide strong reasons to start with this.
--Yakov
Hi Dmitriy,
Do you mean our LLPL library? It has a license, please look here:
https://github.com/pmem/llpl
Regarding the changes made to Ignite, you may refer to the pull request here:
https://github.com/apache/ignite/pull/4381
Thanks,
Mulugeta
-Original Message-
From: Dmitriy Pavlo
What’s perhaps not clear is that the PrunedFilteredScan trait which needs
to be implemented to allow for predicate pushdown does need to return
RDD:
https://spark.apache.org/docs/2.3.0/api/java/org/apache/spark/sql/sources/PrunedFilteredScan.html
IgniteSQLRelation implements this to perform Ignit
My concern here is exactly about internal build processes — removing fabric
from the name of binary archive (with any way) will break lots of them.
There will be no sacrifices, just lots of work for fixing build processes
(where we won’t be able to introduce changes proactively).
Therefore only
Let's focus on what is important here. Our users do not care about our
internal build process.If we could remove the word fabric from the next
release without any significant sacrifices in the build process or making
it less maintainable, I suggest we do it.
D.
On Wed, Aug 1, 2018 at 12:24 PM, Pe
Simple way with some hack and legacy maintenance: accept patch as it is
implemented now.
Hard way: full assembly refactoring and hadoop rejection.
Anyway, after this is merged to master — complete automation systems revision
(TeamCity for example) is required due to heavy hardcode of “fabric” in
Stuart,
>From API standpoint Dataframe is just a Dataset of Rows, so they have the
same set of methods.
You have a valid point, by it's valid for both Dataset and Dataframe in the
same way. If you provide a function that filter Rows in a Dataframe,
current integration would also not take advantag
OK, so what is the plan? How do we get rid of the fabric name?
D.
On Wed, Aug 1, 2018 at 2:21 AM, Anton Vinogradov wrote:
> Since you proposing patch to the community, you are the very man :)
>
> ср, 1 авг. 2018 г. в 12:16, Petr Ivanov :
>
> > You are convincing the wrong person.
> >
> >
> >
>
Val,
Happy to clarify my thoughts. Let’s take an example, say we have an Ignite
cache of Person objects, so in Nikolay’s Ignite Spark SQL implementation you
can currently obtain a DataFrame with a column called “age” because that’s
been registered as a field in Ignite. Then you can do something li
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4398
---
GitHub user aealeksandrov opened a pull request:
https://github.com/apache/ignite/pull/4474
Ignite 2.4.5 p2
For TC run.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2.4.5-p2
Alternatively you can
Hi Mulugeta Mammo,
I've just noticed that repository, what you refer is full fork of Ignite.
How can I see differences with original Ignite?
One more thing, library which you're referencing seems to not contain
license, at least github can not parse it. Apache product has limitations
which librar
Hi,
This link works for me
https://cwiki.apache.org/confluence/display/IGNITE/IEP-26%3A+Adding+Experimental+Support+for+Intel+Optane+DC+Persistent+Memory
Sincerely,
Dmitriy Pavlov
чт, 26 июл. 2018 г. в 15:31, Stanislav Lukyanov :
> Ah, ok, it’s just the ‘.’ at the end of the link. Removed it an
Great, thanks for the update.
ср, 1 авг. 2018 г. в 20:31, Pavel Pereslegin :
> Hello, Dmitriy.
>
> Yes, these tests was previously muted in another test suite.
> I re-muted them again.
>
> 2018-08-01 20:15 GMT+03:00 Dmitriy Pavlov :
> > Hi Ed, Pavel,
> >
> > Do you know, why these test were faile
Hi Dmitriy,
I guess this ticket relates to examples, but new proposal is related only
to test.
Community didn't make an agreement about examples change, so I suggest to
create new ticket (and probably link both tickets) and PR.
Sincerely,
Dmitriy Pavlov
ср, 1 авг. 2018 г. в 20:30, Dmitrii Ryabo
Hello, Dmitriy.
Yes, these tests was previously muted in another test suite.
I re-muted them again.
2018-08-01 20:15 GMT+03:00 Dmitriy Pavlov :
> Hi Ed, Pavel,
>
> Do you know, why these test were failed were failed?
>
> Is it because of new suite?
>
> Sincerely,
> Dmitriy Pavlov
>
> ср, 1 авг. 2
We have ticket [1] for this change.
[1] https://issues.apache.org/jira/browse/IGNITE-6826
2018-08-01 15:58 GMT+03:00 Alexey Zinoviev :
> Great, sometimes I made it manually in local tests. It will be great to
> change the situation.
>
> 2018-08-01 18:22 GMT+06:00 Stanislav Lukyanov :
>
> > +1.
>
Stuart,
I don't see a reason why it would work with DataFrames, but not with
Datasets - they are pretty much the same thing. If you have any particular
thoughts on this, please let us know.
In any case, I would like to hear from Nikolay as he is an implementor of
this functionality. Nikolay, plea
Hi Ed, Pavel,
Do you know, why these test were failed were failed?
Is it because of new suite?
Sincerely,
Dmitriy Pavlov
ср, 1 авг. 2018 г. в 20:12, :
> Hi Ignite Developer,
>
> I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed.
> I hope you can help.
>
> *Recently
Hi Ignite Developer,
I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed. I
hope you can help.
*Recently contributed test failed in master
TxRollbackAsyncWithPersistenceTest.testMixedAsyncRollbackTypes
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24J
Hi,
Failure came from same test (
https://lists.apache.org/thread.html/de7c65383e3cd6c7de1667a1b7c28059761e5ac2c38206b018d90e7c@%3Cdev.ignite.apache.org%3E
)
but from other suite, and already dicsussed.
I will merge https://issues.apache.org/jira/browse/IGNITE-9157 once it is
ready.
Sincerely,
Hi Ignite Developer,
I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed. I
hope you can help.
*New test failure in master
SlowHistoricalRebalanceSmallHistoryTest.testReservation
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=1100469
GitHub user slukyano opened a pull request:
https://github.com/apache/ignite/pull/4473
Ignite 2.4.8
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2.4.8
Alternatively you can review and apply these
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4177
---
This failure is known and happened because of missed maxSize of DataRegion.
All such problems will be fixed in
https://issues.apache.org/jira/browse/IGNITE-9157
2018-08-01 18:12 GMT+03:00 :
> Hi Ignite Developer,
>
> I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed.
> I ho
Hi Ignite Developer,
I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed. I
hope you can help.
*New test failure in master
SlowHistoricalRebalanceSmallHistoryTest.testReservation
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=5380168
GitHub user xtern opened a pull request:
https://github.com/apache/ignite/pull/4472
IGNITE-9148
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/xtern/ignite IGNITE-9148
Alternatively you can review and apply these changes as the
GitHub user EdShangGG opened a pull request:
https://github.com/apache/ignite/pull/4471
IGNITE-9159 Basic 2 TC configuration is halted by failure handler
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite igni
Eduard Shangareev created IGNITE-9159:
-
Summary: Basic 2 TC configuration is halted by failure handler
Key: IGNITE-9159
URL: https://issues.apache.org/jira/browse/IGNITE-9159
Project: Ignite
Sure, https://issues.apache.org/jira/browse/IGNITE-9158.
Regards,
Yury
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Yury Babak created IGNITE-9158:
--
Summary: [ML] Pipeline
Key: IGNITE-9158
URL: https://issues.apache.org/jira/browse/IGNITE-9158
Project: Ignite
Issue Type: New Feature
Components: ml
GitHub user Jokser opened a pull request:
https://github.com/apache/ignite/pull/4470
IGNITE-9157 Optimize data regions memory usage in tests
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9157
Alte
Pavel Kovalenko created IGNITE-9157:
---
Summary: Optimize memory usage of data regions in tests
Key: IGNITE-9157
URL: https://issues.apache.org/jira/browse/IGNITE-9157
Project: Ignite
Issue T
Hi, Igniters.
Currently I'm working on different math stuff over the Apache Ignite and in
a few tasks I need to implement in memory something like this
https://en.wikipedia.org/wiki/Quadtree
I didn't find such index in Apache Ignite, but maybe it's under development
by somebody?
Is it a difficu
Denis Mekhanikov created IGNITE-9156:
Summary: SQL: Impossible to specify equality condition on
sub-select field
Key: IGNITE-9156
URL: https://issues.apache.org/jira/browse/IGNITE-9156
Project: Ig
Great, sometimes I made it manually in local tests. It will be great to
change the situation.
2018-08-01 18:22 GMT+06:00 Stanislav Lukyanov :
> +1.
>
> I don’t see why do we need to fallback to multicast for multi-JVM – let’s
> just set 127.0.0.1:47500..47509 by default,
> it’ll be enough for mos
GitHub user zaleslaw opened a pull request:
https://github.com/apache/ignite/pull/4469
IGNITE-8680: One Hot Encoder (including String Indexing)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8680
A
GitHub user aealeksandrov opened a pull request:
https://github.com/apache/ignite/pull/4468
Ignite 2.4.5.b4
For ignite-2.4.5.b4 TC run.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2.4.5.b4
Altern
+1.
I don’t see why do we need to fallback to multicast for multi-JVM – let’s just
set 127.0.0.1:47500..47509 by default,
it’ll be enough for most (if not all) tests.
Stan
From: Dmitriy Pavlov
Sent: 1 августа 2018 г. 14:21
To: dev@ignite.apache.org
Subject: Re: IP finder in tests
Hi Denis,
Th
Hi Denis,
I also definitely support this change. As an engineer who tightly working
with MakeTeamCityGreenAgain activity, I notice several test suites hanging
related with MulticastIpFinder infinite loops on datagram receiving. Here
is last recorded fail -
https://ci.ignite.apache.org/viewLog.html
GitHub user ilantukh opened a pull request:
https://github.com/apache/ignite/pull/4467
IGNITE-9155 : ExchangeFuture will not complete with Exception on state
change failure.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridga
Ilya Lantukh created IGNITE-9155:
Summary: Exception during cluster state change terminates
ExchangeWorker
Key: IGNITE-9155
URL: https://issues.apache.org/jira/browse/IGNITE-9155
Project: Ignite
Hi Denis,
Thank you for bringing the question here.
I totally support this change.
Sincerely,
Dmitriy Pavlov
ср, 1 авг. 2018 г. в 13:23, Denis Mekhanikov :
> Igniters,
>
> Almost every test in Ignite project has the following pattern: shared
> *TcpDiscoveryVmIpFinder
> *is defined as a field o
Hello!
I think it's a sensible decision that is long overdue.
Regards,
--
Ilya Kasnacheev
2018-08-01 13:22 GMT+03:00 Denis Mekhanikov :
> Igniters,
>
> Almost every test in Ignite project has the following pattern: shared
> *TcpDiscoveryVmIpFinder
> *is defined as a field of a test class, whi
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4454
---
Setting Assignee doesn't mean that the ticket is reserved for that
particular person. If anyone wants to participate in that ticket he can
always ask about that in JIRA or on mailing list. In fact, this is how we
deal with tickets that got stuck on a contributor for a long time.
On Wed, Aug 1, 201
GitHub user ezagumennov opened a pull request:
https://github.com/apache/ignite/pull/4466
IGNITE-9144 client and daemon nodes are supported
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9144
Alter
Hi Vladimir,
please see Code of conduct principles
https://community.apache.org/newbiefaq.html#NewbieFAQ-IsthereaCodeofConductforApacheprojects?
I would be happy to have a chat with you about Apache and open source
principles.
I encourage all Igniters to carefully read thread with ASF fellows rep
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4463
---
Igniters,
Almost every test in Ignite project has the following pattern: shared
*TcpDiscoveryVmIpFinder
*is defined as a field of a test class, which is then used in discovery
configuration in *getConfiguration(...)* method. There are more than 700
test classes with this setup.
But for some reaso
Vladimir Ozerov created IGNITE-9154:
---
Summary: Incorrect new version is used during conflict resolution
in ATOMIC cache
Key: IGNITE-9154
URL: https://issues.apache.org/jira/browse/IGNITE-9154
Projec
Github user ezagumennov closed the pull request at:
https://github.com/apache/ignite/pull/4465
---
Dmitry,
"If something is not happened on mailing list it is not happened" is just
not true. Mailing list is only one of communication channels. I do not see
any reason why I need to discuss assignee on a dev list .This is just spam
for 99% of members.
Again - lets focus on things that matter, rat
Evgenii Zhuravlev created IGNITE-9153:
-
Summary: Accessing cache from transaction on client node, where it
was not accessed yet throws an exception
Key: IGNITE-9153
URL: https://issues.apache.org/jira/browse/I
Hi Dmitriy, Yakov, thank you for your support.
I think if I have an odd hour I will create wiki describing how to create
good ticket.
Igniters,
BTW I found one more way to refer to dev list threads (in addition to
nabble): https://lists.apache.org/list.html?dev@ignite.apache.org
Sincerely,
Dmit
Hi Ilya,
could you please actualize this PR. TC Bot can now detect newly contributed
tests' failures, so I think it is best point to apply you change.
Sincerely,
Dmitriy Pavlov
пт, 25 мая 2018 г. в 18:16, Eduard Shangareev :
> Igniters,
>
> While making review I checked next main-method tests:
GitHub user ezagumennov opened a pull request:
https://github.com/apache/ignite/pull/4465
Ignite 9144
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9144
Alternatively you can review and apply thes
Hi Vladimir,
I think not accepting by community is possible only if PMC will veto
change. I didn't find any reasons why not to do this change and why it can
be vetoed..
I would appreciate if you will become mentor of this change and will assist
to Pavel or other community member to make this happ
Hi Vladimir,
I think I understand your point. I've heard negative feedback. Which is why
I would like to speak it up, I hope other Igniters who disagree with this
assignment will be feeling free to unassign ticket. I would like that noone
was trying to adapt commercial company experience to the Co
Hi Maxim, Evgeniy,
Thank you for researching and finding these issues.
Who could create tickets (probably, newbie) so newcomers can pick up and
fix it?
Sincerely,
Dmitriy Pavlov
ср, 1 авг. 2018 г. в 11:36, Maxim Muzafarov :
> Hello,
>
> I can be wrong, but looks like -
>
> `GridIoManager` not
Igniters,
I've re-read this thread in brief. As far as I know this change is not
coming from some company, so this change will be at least good for healthy
community building.
And I didn't find any obstacles why not to implement approach with new mode
.withFairAsync() for cases user is completely
Since you proposing patch to the community, you are the very man :)
ср, 1 авг. 2018 г. в 12:16, Petr Ivanov :
> You are convincing the wrong person.
>
>
>
> > On 1 Aug 2018, at 12:05, Anton Vinogradov wrote:
> >
> > Peter,
> >
> > We had a discussion about how to do this properly.
> > Proposed s
You are convincing the wrong person.
> On 1 Aug 2018, at 12:05, Anton Vinogradov wrote:
>
> Peter,
>
> We had a discussion about how to do this properly.
> Proposed solution cannot be merged, since it makes code harder than it was.
>
> The only case is to perform complete refactoring and get
Peter,
We had a discussion about how to do this properly.
Proposed solution cannot be merged, since it makes code harder than it was.
The only case is to perform complete refactoring and get rid of all
postfixes and other weird stuff.
For example
-
-
should be definetely removed from code.
с
Agree with Dmitry P.
Guys! Even if you file a ticket on yourself please spend additional 5 mins
to add minimal description to provide idea on the intended changes for the
rest of our community or those who will have to deal with your changes in
future.
--Yakov
Hello,
I can be wrong, but looks like -
`GridIoManager` not a bug, we are checking isEmpty here.
`GridCacheLockImpl` not a bug, variable is volatile.
Suppose, null-check not too critial for these classes, but can be done.
`GridTuple6` - must be fixed.
`GridClientJdkMarshaller` - should be fixe
Pavel Konstantinov created IGNITE-9152:
--
Summary: Web console: add a checkbox 'include in generated project'
Key: IGNITE-9152
URL: https://issues.apache.org/jira/browse/IGNITE-9152
Project: Ignite
Pavel Konstantinov created IGNITE-9151:
--
Summary: Web console: incorrect caches list in 'Import from DB'
modal
Key: IGNITE-9151
URL: https://issues.apache.org/jira/browse/IGNITE-9151
Project: Ign
In general there is nothing wrong with assigning a ticket to someone if you
know that this would not cause negative reaction from assignee side. The
thing is that community has a lot of members who knows each other in person
and in close contact for years. So there is nothing wrong if I assign a
ti
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4363
---
GitHub user zzzadruga opened a pull request:
https://github.com/apache/ignite/pull/4464
IGNITE-8158 Wrap the method afterTestsStopped() call with try/catch bâ¦
â¦lock
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/zzzadruga/ign
Vyacheslav,
Thank you! This seems exactly what I was asking about.
On Wed, 1 Aug 2018 at 10:18 Vyacheslav Daradur wrote:
> Hi, Maxim,
>
> There is information about project components maintainers [1], but I'm
> not sure if it is actual.
>
> [1]
> https://cwiki.apache.org/confluence/display/IGN
Hi, Maxim,
There is information about project components maintainers [1], but I'm
not sure if it is actual.
[1]
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-ReviewProcessandMaintainers
On Wed, Aug 1, 2018 at 9:33 AM Maxim Muzafarov wrote:
>
> Folks,
>
> I
I believe suggested approach will not work with the Spark SQL
relational optimisations which perform predicate pushdown from Spark
to Ignite. For that to work we need both the key/val and the
relational fields in a dataframe schema.
Stuart.
> On 1 Aug 2018, at 04:23, Valentin Kulichenko
> wrote
80 matches
Mail list logo
