Dear community,
I made modifications to the module rest-http.
It works correctly.
Is possible if anybody take my case for the review?
The modifications are:
Support for webpages (test with jsf and primefaces), support for root
context.
Support to JaxWS with RI version.
Support for access to
Mykhaylo Stepanov created IGNITE-12526:
--
Summary: WAL file archiver logging bug
Key: IGNITE-12526
URL: https://issues.apache.org/jira/browse/IGNITE-12526
Project: Ignite
Issue Type: Bug
Excellent, thanks for finding time for that. Ping us if you have any
questions/suggestions and would like to expedite the review process.
-
Denis
On Fri, Jan 10, 2020 at 9:28 AM Emmanouil Gkatziouras
wrote:
> Hi Denis,
>
> More than happy to help.
> Will get into context and see what I can do
Folks,
We paid a little attention to this contribution and presently can't merge
it due to some conflicts. Is anybody interested to take over, resolve
conflicts and complete the contribution?
Emmanouil, considering your expert knowledge of cloud environments, that
might be interesting for you.
Ivan,
That's right, 78 Ignite practitioners took part in the poll. As for this
feedback below,
*Apache Ignite was close to a drop-in replacement technology for a*
*home grown memory-centric data grid used in a legacy product which*
*allowed us to concentrate on building more customer value
Good day,
We have an enquiry from our customer for training on Apache Ignite at Mumbai
- India. I am looking out for support on the same. Please advise.
Thank you,
Nelson D'souza
Span Labs
B209-210, Sagar Tech Plaza
Opp. Hotel Chakra
Sakinaka, Andheri East
Mumbai - 400 072
Cell #
Nikolay Izhikov created IGNITE-12525:
Summary: Spring boot starter
Key: IGNITE-12525
URL: https://issues.apache.org/jira/browse/IGNITE-12525
Project: Ignite
Issue Type: Improvement
Everything is fine.
Merged to master branch.
On Fri, Jan 10, 2020 at 9:48 AM Anton Vinogradov wrote:
> >> Does the issue reproduce in
> >> subsequent runs?
> Unfortunately no.
> We performed 30+ runs without "success".
>
> >> I think we can add an assertion to
> >>
Ivan, if i correctly understand, you suggest additional «expiremental» stuff
only for hiding already leaked RO interface ?
poor approach as for me.
>Folks,
>
>Some thoughts:
>* Releasing an API with known fallacies sounds really bad thing to me.
>It can have a negative consequences for a whole
Guys, what we do with control.sh commands? We can't set experimental
annotation on those commands.
пт, 10 янв. 2020 г., 17:47 Alexey Zinoviev :
> Support the idea with the annotation
>
> пт, 10 янв. 2020 г., 13:11 Вячеслав Коптилин :
>
> > Hello,
> >
> > * We can mark cluster read-only API
Support the idea with the annotation
пт, 10 янв. 2020 г., 13:11 Вячеслав Коптилин :
> Hello,
>
> * We can mark cluster read-only API (without enum) as experimental and
> > change the API in e.g. 2.8.1.
> > * We can try to exclude read-only API from 2.8 at all.
>
> both approaches look good to
Hello,
* We can mark cluster read-only API (without enum) as experimental and
> change the API in e.g. 2.8.1.
> * We can try to exclude read-only API from 2.8 at all.
both approaches look good to me.
By the way, I think it would be a good idea to introduce a new annotation -
@IgniteExperimental
Hello!
I think the third option (exclude publicly-accessible API) is preferable.
Regards,
--
Ilya Kasnacheev
пт, 10 янв. 2020 г. в 12:26, Ivan Pavlukhin :
> Folks,
>
> Some thoughts:
> * Releasing an API with known fallacies sounds really bad thing to me.
> It can have a negative
Folks,
Some thoughts:
* Releasing an API with known fallacies sounds really bad thing to me.
It can have a negative consequences for a whole project for years. My
opinion here that we should resolve the problem with this API somehow
before release.
* We can mark cluster read-only API (without
Quite interesting (IMHO):
* Apache Ignite was close to a drop in replacement technology for a
home grown memory centric data grid used in a legacy product which
allowed us to concentrate on building more customer value rather than
infrastructure.
* Don't let the core grow to big, concentrate on
Denis,
Great! Am I getting it right that there was about 80 respondents?
чт, 9 янв. 2020 г. в 22:14, Denis Magda :
>
> Ignite dev community,
>
> I've closed the questionary and here is raw anonymous data for
> your reference:
>
Guys,
There is also an issue with cluster activation by thin clients. This
feature (.NET thin client API change and protocol change) was added by [1]
without any discussion on dev-list. Sergey's patch [2] deprecate methods
"IgniteCluster.active(boolean)" and "IgniteCluster.active()", but didn't
17 matches
Mail list logo
