[jira] [Created] (IGNITE-12276) Thin client uses Optimized marshaller for TreeSet and TreeMap

[Mikhail Cherkasov (Jira)]

Mikhail Cherkasov created IGNITE-12276:
--

 Summary: Thin client uses Optimized marshaller for TreeSet and 
TreeMap
 Key: IGNITE-12276
 URL: https://issues.apache.org/jira/browse/IGNITE-12276
 Project: Ignite
  Issue Type: Bug
  Components: thin client
Reporter: Mikhail Cherkasov


Thin client uses Optimized marshaller for TreeSet and TreeMap, while thick 
client replace them with BinaryTreeMap/BinaryTreeSet.

As a result it blocks schema changes for stored objects.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: Ignite community is building Calcite-based prototype

[Stamatis Zampetakis]

Hi Denis,

Great initiative! It will be a great opportunity for the two communities to
learn from each other.
Personally, I am too far to attend physically but I find Julian's idea for
an online meeting very appealing.
If there will be such an option I will try to join.

Best,
Stamatis

On Tue, Oct 8, 2019 at 9:54 PM Denis Magda  wrote:

> (Looping in the dev lists as suggested by Julian.)
>
> Julian, Calcite community, let me know what you think about this option.
> We're planning to host an Apache Ignite meetup with our group [1]
> on November 13th or 14th in the San Francisco Bay Area. The desired topic
> is the new Ignite SQL engine based on Calcite. Alex Goncharuk will be
> representing the Ignite community doing the presentation.
>
> Is there anybody from the Calcite community (Julian or mister X) who can
> join the meetup and do a Calcite-intro talk? Alex will be presenting next.
> We would also invite the members of Calcite Bay Area Group. Ignite
> community will take care of all org hurdles.
>
> [1] https://www.meetup.com/Bay-Area-In-Memory-Computing/
> [2] https://www.meetup.com/Apache-Calcite/
>
> -
> Denis
>
>
> On Mon, Oct 7, 2019 at 1:07 PM Julian Hyde  wrote:
>
> > I’m just about to let that meetup group lapse. I have never had the time
> &
> > energy to organize meetups.
> >
> > Maybe we could do an online meeting, that the community could attend?
> > (Subject to the limits set by Zoom or Hangouts or whatever.) Feel free to
> > suggest something on the dev list.
> >
> > Julian
> >
> >
> > On Oct 3, 2019, at 4:16 PM, Denis Magda  wrote:
> >
> > Julian,
> >
> > I just found out that you run an Apache Calcite meetup in Palo Alto:
> > https://www.meetup.com/Apache-Calcite/
> >
> > What do you think if you schedule a meetup in the mid of November? I'm
> > based in Silicon Valley and Alex Goncharuk (one of Ignite veterans and
> > architects) is visiting that month. Alex and I can talk about the reasons
> > why Calcite was selected by Ignite community, covering our architecture
> of
> > today and how it's planned to be changed with Calcite. Plus, the group
> can
> > give valuable feedback.
> >
> > -
> > Denis
> >
> >
> > -- Forwarded message -
> > From: Denis Magda 
> > Date: Wed, Oct 2, 2019 at 3:32 PM
> > Subject: Re: Ignite community is building Calcite-based prototype
> > To: dev 
> > Cc: dev , dev 
> >
> >
> > Julian,
> >
> > Thanks a lot for the references and guidance! I do believe that from now
> > on our community guys will become frequent visitors of yours ;)
> >
> > -
> > Denis
> >
> >
> > On Wed, Oct 2, 2019 at 12:40 PM Julian Hyde  wrote:
> >
> >> Denis,
> >>
> >> I’ve been a follower and admirer of Ignite for several years, so I am
> >> delighted that you are considering Calcite.
> >>
> >> Ask questions on the dev list, log JIRA cases if you find them, and
> we’ll
> >> do our best to help.
> >>
> >> I’d like to bring to your attention RelBuilder. Some people want to go
> >> from SQL text to executable plan, but others want to drop in at the
> >> relational algebra level, and RelBuilder is a convenient interface for
> the
> >> latter.
> >>
> >> (The other) Julian
> >>
> >>
> >> > On Oct 1, 2019, at 3:43 PM, Denis Magda  wrote:
> >> >
> >> > Hi Julian,
> >> >
> >> > Nice to e-meet you and thanks for being ready to help! Hopefully, the
> >> > Ignite community will be able to contribute valuable changes back to
> >> > Calcite as part of this activity - "pay good for good" :)
> >> >
> >> > You are right that distributed computing, massive-parallel processing,
> >> and
> >> > calculations/querying at scale is what Ignite is targeted for.
> However,
> >> > while Drill is designed for analytics and IoTDB is for time-series,
> >> Ignite
> >> > is primarily used for OLTP with an increasing number of real-time
> >> analytics
> >> > use cases (no adhoc).
> >> >
> >> > Let's stay in touch!
> >> >
> >> > -
> >> > Denis
> >> >
> >> >
> >> > On Tue, Oct 1, 2019 at 6:42 AM Julian Feinauer <
> >> j.feina...@pragmaticminds.de>
> >> > wrote:
> >> >
> >> >> Hi Igor,
> >> >>
> >> >> I agree that it should be rather similar to what Drill did as
> >> distributed
> >> >> computing also is a big concern for Ignite, I guess, right?
> >> >>
> >> >> Julian
> >> >>
> >> >> Am 01.10.19, 15:06 schrieb "Seliverstov Igor"  >:
> >> >>
> >> >>Guys,
> >> >>
> >> >>The better link:
> >> >>
> >>
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-37%3A+New+query+execution+engine
> >> >> <
> >> >>
> >>
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-37:+New+query+execution+engine
> >> >>>
> >> >>
> >> >>Almost everything you may see by the link is the same as Drill
> guys
> >> >> already did, the difference is in details but the idea is the same.
> >> >>
> >> >>Of course we’ll face many issues while development and I'll
> >> appreciate
> >> >> if some of you assist us.
> >> >>
> >> >>Regards,
> >> >>Igor
> >> >>
> >> >>> 1 окт. 2019 г., в 12:32, Julian Feinauer <
> >> 

Re: Broken image links in under-the-hood articles in wiki

[Dmitriy Pavlov]

Hi Ivan, thanks for bringing this here, it is definitely needed to be fixed.

There is the same issue for one picture here, as well,
https://cwiki.apache.org/confluence/display/IGNITE/Ignite+Persistent+Store+-+under+the+hood

I'll replace images in the wiki as well, hopefully, by the end of the
weekend.

Sincerely,
Dmitriy Pavlov

PS, I've shared links to new images sources in the Slack channel.

ср, 9 окт. 2019 г. в 15:19, Ivan Pavlukhin :

> Hi,
>
> I faced that "Ignite Durable Memory - under the hood" [1] page has
> some broken image links.
>
> Dmitriy Pavlov, perhaps you as an author know how to deal with it.
>
> Folks, if you saw other broken links do not hesitate to write to this
> thread.
>
> [1]
> https://cwiki.apache.org/confluence/display/IGNITE/Ignite+Durable+Memory+-+under+the+hood
>
> --
> Best regards,
> Ivan Pavlukhin
>

[jira] [Created] (IGNITE-12275) Make byte order in Persistence pages configurable

[Ilya Kasnacheev (Jira)]

Ilya Kasnacheev created IGNITE-12275:


 Summary: Make byte order in Persistence pages configurable
 Key: IGNITE-12275
 URL: https://issues.apache.org/jira/browse/IGNITE-12275
 Project: Ignite
  Issue Type: Improvement
  Components: persistence
Reporter: Ilya Kasnacheev


Right now we force it to be in LITTLE_ENDIAN, but we don't read it in fixed 
order, which leads to failures.

After IGNITE-12271 it will be changed to nativeOrder().

We should make it configurable so that persistence files may be moved between 
nodes of different archs.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Broken image links in under-the-hood articles in wiki

[Ivan Pavlukhin]

Hi,

I faced that "Ignite Durable Memory - under the hood" [1] page has
some broken image links.

Dmitriy Pavlov, perhaps you as an author know how to deal with it.

Folks, if you saw other broken links do not hesitate to write to this thread.

[1] 
https://cwiki.apache.org/confluence/display/IGNITE/Ignite+Durable+Memory+-+under+the+hood

-- 
Best regards,
Ivan Pavlukhin

[jira] [Created] (IGNITE-12274) [ML] DecisionTree works incorrectly if maxDeep > amount of features

[Alexey Zinoviev (Jira)]

Alexey Zinoviev created IGNITE-12274:


 Summary: [ML] DecisionTree works incorrectly if maxDeep > amount 
of features
 Key: IGNITE-12274
 URL: https://issues.apache.org/jira/browse/IGNITE-12274
 Project: Ignite
  Issue Type: Bug
  Components: ml
Affects Versions: 2.9
Reporter: Alexey Zinoviev
Assignee: Alexey Zinoviev
 Fix For: 2.9


We have a problem in two places: 

null nodes could be created here *MeanDecisionTreeLeafBuilder.createLeafNode* 
method in the row *return aa != null ? new DecisionTreeLeafNode(aa[0]) : null;*

Probably, this situation is arising then the amount of features is smaller than 
maxDeep



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

IGNITE-12236 RepositoryFactorySupport#getQueryLookupStrategy no longer overriden in IgniteRepositoryFactory

[thibaut]

Hello,

New guy here.

When I was trying to use ignite with an up to date version of
spring-data-commons I ended up having some issues since ignite uses version
2.0.9. (see  IGNITE-12236
  )
As of 2.1.0 RepositoryFactorySupport#getQueryLookupStrategy changed its
signature with this  commit

 
.

Already made a PR but I realized after the fact that there is a few issues
asking to update but not one seems to fix this problem:
IGNITE-12129

  
IGNITE-12259   

Maybe 12129 and my issue should be merged (its pom + this
IgniteRepositoryFactory).

What do you think?

BR,
Thibaut



--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

[jira] [Created] (IGNITE-12273) Slow TX recovery

[Anton Vinogradov (Jira)]

Anton Vinogradov created IGNITE-12273:
-

 Summary: Slow TX recovery
 Key: IGNITE-12273
 URL: https://issues.apache.org/jira/browse/IGNITE-12273
 Project: Ignite
  Issue Type: Task
Reporter: Anton Vinogradov
Assignee: Anton Vinogradov


TX recovery cause B*N*2 GridCacheTxRecoveryRequest messages sending (B - 
backups, N - prepared txs amount).
Seems, we able to perform recovery more efficiently.
For example, we may send only B*B*2 messages, accumulates txs together.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (IGNITE-12272) Delayed TX recovery

[Anton Vinogradov (Jira)]

Anton Vinogradov created IGNITE-12272:
-

 Summary: Delayed TX recovery
 Key: IGNITE-12272
 URL: https://issues.apache.org/jira/browse/IGNITE-12272
 Project: Ignite
  Issue Type: Task
Reporter: Anton Vinogradov
Assignee: Anton Vinogradov


TX recovery now starts in delayed way.
IGNITE_TX_SALVAGE_TIMEOUT = 100 which cause 100+ ms delay on recovery.
Seems, we able to get rig of this delay to make recovery faster.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: Nabble message wrapping

[Denis Magda]

The response of the INFRA team:

The quotes you're referring to are generated by end-user mail clients, and
have nothing to do with our mailing list software. This is, in part, why
most ASF folks use an inline quoting style as opposed to the more common
top-posting style. There is nothing Infra can do about the quoting style of
list participants, sorry.

Let's use the inline quoting.

-
Denis


On Tue, Sep 17, 2019 at 3:11 AM Denis Mekhanikov 
wrote:

> I've created an INFRA ticket:
> https://issues.apache.org/jira/browse/INFRA-19042
>
> Denis
> On 12 Sep 2019, 00:46 +0300, Denis Magda , wrote:
> > Thanks for sharing details.
> >
> > 2. Change the ezmlm configuration to match the one of the users list. We
> > > need to find a person who has access to the Apache infra in order to
> do this
> >
> >
> > We can open a ticket for ASF INFRA. Could you please do that and see what
> > they say?
> >
> > -
> > Denis
> >
> >
> > On Wed, Sep 11, 2019 at 1:36 AM Denis Mekhanikov 
> > wrote:
> >
> > > Denis,
> > >
> > > I did some investigation on this and started a Nabble support thread:
> > > http://support.nabble.com/Line-wrapping-in-quotes-td7604136.html
> > > It turned out, that Nabble has a little to do with it. It’s the mail
> list
> > > itself.
> > >
> > > When you send a plain text message to the dev list either from Nabble
> or
> > > in any other way, it’s getting wrapped to be 80 characters wide.
> > > HTML messages don’t have this issue. Nabble uses plain text by default.
> > > User list doesn’t wrap quotes though, even if you use plain text
> format.
> > > You can see that my reply in the following thread is wrapped, but not
> the
> > > quote:
> > >
> http://apache-ignite-users.70518.x6.nabble.com/Ignition-Start-Timeout-if-connection-is-unsuccessful-td29289.html
> > >
> > > I see two possibilities of solving this issue:
> > >
> > > 1. Make Nabble always send messages in HTML format somehow. The issue
> will
> > > still occur for other mail clients though.
> > > 2. Change the ezmlm configuration to match the one of the users list.
> We
> > > need to find a person who has access to the Apache infra in order to do
> > > this.
> > >
>