Vote has to be closed due to unclear EA versioning process.
A new build will be resubmitted today.
--Yakov
Igniters,
Wiki page https://apacheignite.readme.io/v1.5 now public beta.
Raul,
I've added 1.6 space as a copy of 1.5.
But I gain no results at OSGi search.
Could you please specify what pages should be removed from 1.5 or revome
them by yourself?
On Mon, Nov 30, 2015 at 6:18 PM, Yakov Zhdanov wrote:
> Raul, as far as commits - they are mostly fixes for functionality
Yakov, can you please send [CANCEL][VOTE] email?
On Mon, Nov 30, 2015 at 11:42 PM, Yakov Zhdanov wrote:
> Guys, let's close this vote thread. I think we will resubmit another build
> today evening. I will also send out my vision on EA process and I ask
> everyone to respond on that thread.
>
> -
Pavel Konstantinov created IGNITE-2038:
--
Summary: 'Connection to Ignite Web Agent is not established'
dialog doesn't close after agent is started
Key: IGNITE-2038
URL: https://issues.apache.org/jira/browse/IG
As for me I also think it is better to preserve current behaviour and add
note to documentation.
I like to treat LOCAL cache as HashMap with cool features.
I created newbie "IGNITE-2037 Update javadocs and documentation about LOCAL
cache could be created on client node"
https://issues.apache.org/j
Guys, let's close this vote thread. I think we will resubmit another build
today evening. I will also send out my vision on EA process and I ask
everyone to respond on that thread.
--Yakov
Alexey Kuznetsov created IGNITE-2037:
Summary: Update javadocs and documentation about LOCAL cache could
be created on client node
Key: IGNITE-2037
URL: https://issues.apache.org/jira/browse/IGNITE-2037
Pavel Konstantinov created IGNITE-2036:
--
Summary: Reset password link in the email doesn't redirect to
reset password page
Key: IGNITE-2036
URL: https://issues.apache.org/jira/browse/IGNITE-2036
I think there is nothing bad in this. I would leave it as is and just
properly fix javadoc that local cache can be created.
--Yakov
2015-12-01 10:21 GMT+03:00 Denis Magda :
> Alex,
>
> This is seems to be one more poor documented feature :)
>
> To be serious my preference is to throw an exceptio
Who can change a preselected mirror to either http or ftp by default?
On 12/1/2015 9:07 AM, Yakov Zhdanov wrote:
You should select "Selected mirror" combobox under the table.
--Yakov
2015-12-01 8:33 GMT+03:00 Valentin Kulichenko
:
Igniters,
I just found out that all release download links on
Alex,
This is seems to be one more poor documented feature :)
To be serious my preference is to throw an exception in response to an
attempt to create a LOCAL cache on a client node because client nodes
can't store cache data by notion.
Any other thoughts?
--
Denis
On 11/30/2015 12:41 PM,
On Mon, Nov 30, 2015 at 9:02 AM, Andrey Kornev
wrote:
>
> Neither Coherence nor Hazelcast require the EP to be stateless and
> side-effect free. Even better Hazelcast makes the choice explicit by
> providing the backup aware processor API and it's then up to the user to
> ensure statelessness etc
On Mon, Nov 30, 2015 at 10:44 PM, Pavel Tupitsyn
wrote:
> Dmitry, thank you, I see it.
>
> However, I'm concerned that site name is not consistent with the main one:
> * apacheignite.readme.io
> * apache-ignite-net.readme.io
>
> I think it first part should be the same: apacheignite-net.readme.io
Dmitry, thank you, I see it.
However, I'm concerned that site name is not consistent with the main one:
* apacheignite.readme.io
* apache-ignite-net.readme.io
I think it first part should be the same: apacheignite-net.readme.io.
Thanks,
On Tue, Dec 1, 2015 at 5:27 AM, Dmitriy Setrakyan
wrote:
As most of you probably know FOSDEM 2016 (the biggest,
100% free open source developer conference) is right
around the corner:
https://fosdem.org/2016/
We hope to have an ASF booth and we would love to see as
many ASF projects as possible present at various tracks
(AKA Developer rooms):
htt
You should select "Selected mirror" combobox under the table.
--Yakov
2015-12-01 8:33 GMT+03:00 Valentin Kulichenko :
> Igniters,
>
> I just found out that all release download links on [1] are broken (at
> least in Chrome).
>
> It seems that there are some template placeholders that are not rep
Igniters,
I just found out that all release download links on [1] are broken (at
least in Chrome).
It seems that there are some template placeholders that are not replaced
properly, because the links look like this:
https://ignite.apache.org/[preferred]/[distdir]/1.4.0/apache-ignite-1.4.0-src.zi
Pavel,
I have created Apache Ignite for .NET space in readme and added you to the
project. You should have an invite in your inbox.
D.
On Mon, Nov 30, 2015 at 10:01 AM, Pavel Tupitsyn
wrote:
> Hello Igniters,
>
> We have Apache Ignite readme.io site published:
> https://apacheignite.readme.io/
On Mon, Nov 30, 2015 at 3:45 PM, Raul Kripalani wrote:
> On Mon, Nov 30, 2015 at 11:25 PM, Andrey Kornev
> wrote:
>
> > And since you've asked for opinions, it's also my opinion that the
> > discussion about the naming was a non-consequential bikeshedding (
> > https://en.wikipedia.org/wiki/Park
On Mon, Nov 30, 2015 at 12:39 PM, Raul Kripalani wrote:
>
> We have opposite views here. To me, early access versions are ephemeral.
> They are only legit until the final version is released. By doing that, you
> run the risk that "forgetful" users who once tried an EA, keep using it
> forever ev
On Mon, Nov 30, 2015 at 11:25 PM, Andrey Kornev
wrote:
> And since you've asked for opinions, it's also my opinion that the
> discussion about the naming was a non-consequential bikeshedding (
> https://en.wikipedia.org/wiki/Parkinson's_law_of_triviality) and
> potentially causing unnecessary del
Guys, there is obviously a difference of opinions here. If I can make a
suggestion, let’s agree on the versioning scheme and proceed. I like Raul’s
suggestion for EA-01/02/03/etc… If there are no objections, let’s follow
this scheme going forward.
D.
On Mon, Nov 30, 2015 at 3:11 PM, Raul Kripalan
Raul,
I'm not associated with GG and my opinion is that Yakov's naming is good enough.
And since you've asked for opinions, it's also my opinion that the discussion
about the naming was a non-consequential bikeshedding
(https://en.wikipedia.org/wiki/Parkinson's_law_of_triviality) and potentiall
On Mon, Nov 30, 2015 at 8:41 PM, Yakov Zhdanov wrote:
> Raul, I don't see anything wrong with this approach. EA2 can follow EA.
> Versioning of EAs does not matter too much to me :)
>
If you are wanting to push EAs to Central, then we must have a predictable
versioning scheme. Publishing to Cent
Yakov,
We were having an active discussion in the dev mailing list about the name
of this version.
The discussion had not concluded. It is not respectful for you to override
the disagreement and take a decision.
I would like to hear the opinion of other members outside of GG about the
naming.
W
Dear Sirs!
We have uploaded release candidate to
https://dist.apache.org/repos/dist/dev/ignite/1.5.0-EA-rc2/
This is very important release containing initial versions of Ignite.NET
and Ignite C++ and many other important features and improvements.
We want community to test this EA in order to ga
Raul, I don't see anything wrong with this approach. EA2 can follow EA.
Versioning of EAs does not matter too much to me :)
You can download EAP build of IntellijIdea, although Idea 14 is available
now for more than 1 year already.
Btw, here is one more example of keeping EA versions in repo -
ht
Ilya Suntsov created IGNITE-2035:
Summary: Misprint in javadoc
Key: IGNITE-2035
URL: https://issues.apache.org/jira/browse/IGNITE-2035
Project: Ignite
Issue Type: Bug
Components: bu
Any others? I need some more convincing :)
That Hazelcast does it doesn't mean that it's correct SW Engineering
practice. Perhaps they don't have a public Maven repo (probably that's the
reason) where they can publish their EA in a staging area. The ASF does
(advantage) and therefore we can use th
Hi
Some companies provide EA releases in maven:
https://oss.sonatype.org/content/repositories/releases/com/hazelcast/hazelcast/3.6-EA/
On Mon, Nov 30, 2015 at 9:39 PM, Raul Kripalani wrote:
> On Mon, Nov 30, 2015 at 5:23 PM, Yakov Zhdanov
> wrote:
>
> > 1. I see nothing wrong in having EA pe
On Mon, Nov 30, 2015 at 5:23 PM, Yakov Zhdanov wrote:
> 1. I see nothing wrong in having EA perpetually available. I would even
> prefer all vendors to keep all EA versions available just for tracking and
> history purposes.
>
We have opposite views here. To me, early access versions are ephemer
Hello Igniters,
We have Apache Ignite readme.io site published:
https://apacheignite.readme.io/
I'm working on a similar site for Apache Ignite .NET and have some
questions:
1) Publishing. Should I file an open source application? How did we do it
before?
2) Naming. Should it be apacheignite-dotn
Thanks Yujue Li! I will add the link to this documentation on our website.
Please keep us posted on your progress.
On Mon, Nov 30, 2015 at 4:17 AM, 李玉珏@163 <18624049...@163.com> wrote:
> Hi：
>
> As of today, the data grid has been translated and completed.
>
> I tried to put the HTML on the GIT r
On Mon, Nov 30, 2015 at 9:17 AM, Raul Kripalani wrote:
> On Mon, Nov 30, 2015 at 5:05 PM, Yakov Zhdanov
> wrote:
>
> > Raul, every build submitted for vote is RC (so, on first iteration this
> > will be 1.5.0-EA-RC1). Once accepted RC gets stripped off and we get
> > official release. My idea is
Raul, I see your point. However
1. I see nothing wrong in having EA perpetually available. I would even
prefer all vendors to keep all EA versions available just for tracking and
history purposes.
2. Even if we choose not to do maven release we can still go with EA and
just leave staging repo unre
Agree, +1 for the EA. We are preparing to change the default marshaller, so
it will be great to obtain the feedback from the community and see if we
missed something.
Dmitry, it will be 1.5.0-EA.
--Yakov
2015-11-30 20:10 GMT+03:00 Dmitriy Setrakyan :
> On Mon, Nov 30, 2015 at 9:09 AM, Yakov Zhdanov
> wrote:
>
> > Guys, common practice when dealing with EA builds is to have EA (or EA1),
> > EA2, etc versions. So, I would prefer to follow this process.
> >
>
>
On Mon, Nov 30, 2015 at 5:05 PM, Yakov Zhdanov wrote:
> Raul, every build submitted for vote is RC (so, on first iteration this
> will be 1.5.0-EA-RC1). Once accepted RC gets stripped off and we get
> official release. My idea is to have EA available via maven and from the
> website.
>
Aha, I se
Next EA will be EA2 but I hope it will be RC1
On Mon, Nov 30, 2015 at 8:13 PM, Dmitriy Setrakyan
wrote:
> On Mon, Nov 30, 2015 at 9:12 AM, Yakov Zhdanov
> wrote:
>
> > Dmitry, it will be 1.5.0-EA.
> >
>
> How about 1.5.0-EA1? We may have more than one EA release.
>
>
> >
> > --Yakov
> >
> > 201
If so we will have EA2.
--Yakov
2015-11-30 20:13 GMT+03:00 Dmitriy Setrakyan :
> On Mon, Nov 30, 2015 at 9:12 AM, Yakov Zhdanov
> wrote:
>
> > Dmitry, it will be 1.5.0-EA.
> >
>
> How about 1.5.0-EA1? We may have more than one EA release.
On Mon, Nov 30, 2015 at 9:00 AM, Alexey Goncharuk <
alexey.goncha...@gmail.com> wrote:
> I think this is a great idea, however this exercise only makes sense if
> FindBugs profile is plugged to CI and provides continuous checks for the
> new code being committed.
> …
> Hopefully, somebody from the
On Mon, Nov 30, 2015 at 9:12 AM, Yakov Zhdanov wrote:
> Dmitry, it will be 1.5.0-EA.
>
How about 1.5.0-EA1? We may have more than one EA release.
>
> --Yakov
>
> 2015-11-30 20:10 GMT+03:00 Dmitriy Setrakyan :
>
> > On Mon, Nov 30, 2015 at 9:09 AM, Yakov Zhdanov
> > wrote:
> >
> > > Guys, comm
On Mon, Nov 30, 2015 at 9:09 AM, Yakov Zhdanov wrote:
> Guys, common practice when dealing with EA builds is to have EA (or EA1),
> EA2, etc versions. So, I would prefer to follow this process.
>
Yakov, what would be the final version of the downloadable EA release?
>
> --Yakov
>
> 2015-11-30
Guys, common practice when dealing with EA builds is to have EA (or EA1),
EA2, etc versions. So, I would prefer to follow this process.
--Yakov
2015-11-30 20:04 GMT+03:00 Dmitriy Setrakyan :
> On Mon, Nov 30, 2015 at 8:57 AM, Raul Kripalani wrote:
>
> > On Mon, Nov 30, 2015 at 4:30 PM, Yakov Zh
Raul, every build submitted for vote is RC (so, on first iteration this
will be 1.5.0-EA-RC1). Once accepted RC gets stripped off and we get
official release. My idea is to have EA available via maven and from the
website.
--Yakov
2015-11-30 19:57 GMT+03:00 Raul Kripalani :
> On Mon, Nov 30, 201
On Mon, Nov 30, 2015 at 8:57 AM, Raul Kripalani wrote:
> On Mon, Nov 30, 2015 at 4:30 PM, Yakov Zhdanov
> wrote:
>
> > Please let me know your opinion. If community agrees I will submit
> 1.5.0-EA
> > for vote in a few hours.
> >
>
> Would this be an EA or a RC?
>
I think we should definitely
Thank you, Alexey!
By stating that "sending a serialized EntryProcessor should be cheaper" you
implicitly assume that the cache entry is big and the computation done by the
processor is cheap. But what if it's not the case? What if the computation
itself is quite expensive and depends on extern
I think this is a great idea, however this exercise only makes sense if
FindBugs profile is plugged to CI and provides continuous checks for the
new code being committed.
Since Alexey K. already has some feedback for the first run, I will
cooperate with him to create a minimal set of checks that w
On Mon, Nov 30, 2015 at 4:30 PM, Yakov Zhdanov wrote:
> Please let me know your opinion. If community agrees I will submit 1.5.0-EA
> for vote in a few hours.
>
Would this be an EA or a RC?
Regards,
*Raúl Kripalani*
PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
Mess
I'm fully agree with Yakov. We plain to release massive changes and I think
that it's good chance for community to play with new features and we can
get more feedback.
On Mon, Nov 30, 2015 at 7:32 PM, Alexey Kuznetsov
wrote:
> +1 for EA
>
> On Mon, Nov 30, 2015 at 11:30 PM, Yakov Zhdanov
> wrot
+1 for EA
On Mon, Nov 30, 2015 at 11:30 PM, Yakov Zhdanov wrote:
> Guys,
>
> Our plan was to release over the weekend, but unfortunately that didn’t
> happen due to a few bugs. And even though we have fixed all the discovered
> issues I am still not comfortable with releasing the final version.
Guys,
Our plan was to release over the weekend, but unfortunately that didn’t
happen due to a few bugs. And even though we have fixed all the discovered
issues I am still not comfortable with releasing the final version. Having
the great number of functionality introduced in 1.5 including (but not
Raul, as far as commits - they are mostly fixes for functionality, but do
not add new features.
Can someone create 1.6 space and move OSGi articles there? Perhaps, Anton
V. can do it?
--Yakov
2015-11-30 16:42 GMT+03:00 Raul Kripalani :
> Dmitriy,
>
> I'm not going to judge if the communication
Ilya Suntsov created IGNITE-2034:
Summary: Need to print information about marshaller in log (for
yardstick-ignite)
Key: IGNITE-2034
URL: https://issues.apache.org/jira/browse/IGNITE-2034
Project: Ign
GitHub user ashutakGG opened a pull request:
https://github.com/apache/ignite/pull/282
Fix GridNioSelfTest.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ashutakGG/incubator-ignite
ignite-GridNioSelfTest
Alternatively you can
Github user ashutakGG closed the pull request at:
https://github.com/apache/ignite/pull/281
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is e
GitHub user ashutakGG opened a pull request:
https://github.com/apache/ignite/pull/281
GridNioServer will try to connect to the next ports if current port already
busy.
GridNioSelfTest tests fail on TC sometimes with the following exception:
org.apache.ignite.IgniteCheckedE
Dmitriy,
I'm not going to judge if the communication of release timelines is
efficient. In fact, the release has still not been made and there's no
traffic in the ML about what's going on. Commits are still being pushed, no
one knows anything. It seems communication is internal between committers.
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/260
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enab
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/271
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enab
Hi：
As of today, the data grid has been translated and completed.
I tried to put the HTML on the GIT repository, but the effect was not
good. As a temporary solution, I'm going to put the HTM on the
www.zybuluo.com site, and I also use the site to provide the tools for
translation.
By my En
Andrey,
If I leave behind my knowledge about Ignite internals, my expectation would
be that an EntryProcessor is invoked on all affinity - both primary and
backup - nodes in the grid. The main reason behind this expectation is that
usually a serialized EntryProcessor instance is smaller than resul
Dmitriyff created IGNITE-2033:
-
Summary: Refactoring summary page
Key: IGNITE-2033
URL: https://issues.apache.org/jira/browse/IGNITE-2033
Project: Ignite
Issue Type: Sub-task
Reporter
Denis Magda created IGNITE-2032:
---
Summary: Filters passed to ScanQuery are not redeployed when
originating from a client node
Key: IGNITE-2032
URL: https://issues.apache.org/jira/browse/IGNITE-2032
Proj
Ignites,
If I start client node and create local cache on it seems that local cache
created on client node.
Is this correct behaviour or not not?
>From API consistency - seems not, because PARTITIONED and REPLICATED caches
throw exception.
But from user point it may be very useful in some cases,
Igniters,
I glad to announce a contribution to Ignite [1]. It's pretty cool separate
project which can be used as GUI for Ignite (currently for topology and
cache) and works via Ignite REST API.
Currently, I am corresponding with the contributor via user list [2].
I think, someone from commiters
Vladimir Ershov created IGNITE-2031:
---
Summary: Add the possibility to adress local ignite instance
inside lambda.
Key: IGNITE-2031
URL: https://issues.apache.org/jira/browse/IGNITE-2031
Project: Ign
68 matches
Mail list logo
