From dev-return-34493-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Tue May 15 11:56:54 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 46454180634 for ; Tue, 15 May 2018 11:56:54 +0200 (CEST) Received: (qmail 49500 invoked by uid 500); 15 May 2018 09:56:52 -0000 Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list dev@ignite.apache.org Received: (qmail 49489 invoked by uid 99); 15 May 2018 09:56:52 -0000 Received: from mail-relay.apache.org (HELO mailrelay1-lw-us.apache.org) (207.244.88.152) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 May 2018 09:56:52 +0000 Received: from mail-ot0-f179.google.com (mail-ot0-f179.google.com [74.125.82.179]) by mailrelay1-lw-us.apache.org (ASF Mail Server at mailrelay1-lw-us.apache.org) with ESMTPSA id A366A6E3 for ; Tue, 15 May 2018 09:56:51 +0000 (UTC) Received: by mail-ot0-f179.google.com with SMTP id h8-v6so17754317otb.2 for ; Tue, 15 May 2018 02:56:51 -0700 (PDT) X-Gm-Message-State: ALKqPwexiNhTScRpuYSXOuOdKtbaoGEC9ahkZ07RmQTlAbGPVNYYajoj U/Y8OccY9aW612nZBKuyK2Ng0um7c6PT3agLPHMB4Q== X-Google-Smtp-Source: AB8JxZqKmiCfB9YvinwSajP71AUgLAD7SVD374TIx7DoPxB3XBwcpqafbRCjffn3LkDVXdZn8VtTS/95ZVwHtPJSj3c= X-Received: by 2002:a9d:1de4:: with SMTP id w33-v6mr10208088otw.128.1526378210956; Tue, 15 May 2018 02:56:50 -0700 (PDT) MIME-Version: 1.0 Received: by 10.201.58.47 with HTTP; Tue, 15 May 2018 02:56:10 -0700 (PDT) In-Reply-To: References: From: Dmitriy Setrakyan Date: Tue, 15 May 2018 12:56:10 +0300 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: supporting different configuration format json,yaml... To: dev Content-Type: multipart/alternative; boundary="0000000000000eb31d056c3b9f1b" --0000000000000eb31d056c3b9f1b Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I still do not understand *why* do we need to add additional formats for the configuration. Can you please show me some users on the user@ list or stack overflow who asked for it? I just want to make sure that if we are creating work for ourselves, then someone actually needs it. D. On Tue, May 15, 2018 at 12:41 PM, Igor Sapego wrote: > I don't think we need to add new formats on server side as there may > be a lot of different formats for different clients. On the other hand, > supporting additional formats may be non trivial and error-prone, while > adding little to a user experience. > > For clients, I see no problem in adding for example JSON -> XML > converter on client side, if JS folks need it. > > For servers, adding another configuration format just to make it more > familiar to users with no Java background seems unreasonable to me > as well, as there still going to be Java class names in configuration > and Spring approach in general. > > What will change is a XML formatting is going to change to JSON > formatting, which has no much sense to me, as everyone know XML. > It is Spring approach what can be confusing to non-Java users, and > it is not going to change regardless of format. > > Best Regards, > Igor > > On Tue, May 15, 2018 at 12:15 PM, Dmitriy Govorukhin < > dmitriy.govorukhin@gmail.com> wrote: > > > Folks, > > > > I guess when work on a thin client will be completed, we get more > newcomers > > who use go/python/php/js. > > And we can do ignite more friendly for them, support familiar formats f= or > > configuration. > > > > On Tue, May 15, 2018 at 12:13 PM, Dmitry Pavlov > > wrote: > > > > > Hi Igniters, > > > > > > In general I aggree with adding new format, e.g. JSON is more popular > > than > > > XML for new applications. > > > > > > In the same time I've never heard that user asked this in the user > list. > > Or > > > did I missed such topics? > > > > > > Sincerely, > > > Dmitriy Pavlov > > > > > > =D0=B2=D1=82, 15 =D0=BC=D0=B0=D1=8F 2018 =D0=B3. =D0=B2 9:31, Pavel T= upitsyn : > > > > > > > Dmitriy, > > > > > > > > We don't need to support different config formats on server in orde= r > to > > > add > > > > that to thin clients. > > > > > > > > Thin client protocol provides a way to create a cache with custom > > config > > > > [1]. > > > > It is up to thin client library authors to use any config format th= ey > > > like > > > > and then convert it into protocol-defined format. > > > > > > > > C# thin client uses custom format, for example, not Spring. > > > > > > > > [1] > > > > > > > > https://apacheignite.readme.io/docs/binary-client- > > > protocol-cache-configuration-operations#section-op_cache_ > > > create_with_configuration > > > > > > > > On Mon, May 14, 2018 at 7:54 PM, Ivan Rakov > > > wrote: > > > > > > > > > Dmitry, > > > > > > > > > > We rely on Spring Framework when we start Ignite node from XML > > > > > configuration. Spring doesn't easily support another formats of > > > > > configuration files. I think, the main reason for this is built-i= n > > > > ability > > > > > to validate configuration via XML Schema. We can surely hack this > > > around > > > > (I > > > > > bet there are existing libraries for configuring Spring with JSON= ), > > > but I > > > > > don't think that anyone suffered from inability to statically > > configure > > > > > Ignite with json/yaml. > > > > > > > > > > Regarding thin clients: makes sense. I suppose necessary mappings > > will > > > be > > > > > implemented as a part of thin client. > > > > > > > > > > Best Regards, > > > > > Ivan Rakov > > > > > > > > > > > > > > > On 14.05.2018 18:58, Dmitriy Govorukhin wrote: > > > > > > > > > >> Hi, Igniters! > > > > >> > > > > >> As far as I know, many people work on a thin client for differen= t > > > > language > > > > >> (go,js,php...). > > > > >> Are there any reasons why ignite does not support yaml or json > > format > > > > for > > > > >> configuration? or some other popular format? > > > > >> In future, it can help to integrate with thin clients, for > example, > > js > > > > >> client may want to dynamic cache start, he passes cache > > configuration > > > > (in > > > > >> native format, for js it will json) through TCP, Ignite node > unwrap > > > and > > > > >> remap to java representation and dynamic start cache. > > > > >> > > > > >> > > > > > > > > > > > > > > > --0000000000000eb31d056c3b9f1b--