On Tue, Aug 22, 2017 at 4:43 AM, Yakov Zhdanov wrote:
> >Not really. What if the user configured Ignite from Java API, without any
> >XML. What will be saved? To prevent this ambiguity, I think the cleanest
> >way is to ask user to save the configuration to a file explicitly.
>
> I think it does
I am a bit confused. How about "select * from SomeTable where myCriteria >
1"?
On Tue, Aug 22, 2017 at 9:16 AM, Vladimir Ozerov
wrote:
> My strong recommendation here is to think carefully of all potential use
> cases first, so that we end up with consistent and extendable API. This
> filters co
+1
On Tue, Aug 22, 2017 at 5:30 PM, Denis Magda wrote:
> Seems it’s time to upgrade ignite-spark module once again. Soon we should
> start getting more issues related to Spark 2.2.0 incompatibility.
>
> —
> Denis
>
> > Begin forwarded message:
> >
> > From: "Denis Magda (JIRA)"
> > Subject: [ji
On Tue, Aug 22, 2017 at 7:19 AM, Aleksei Zaitsev
wrote:
> If newer versions of Ignite delivers with benchmarks I think it's
> redundant to support one more project.
>
Well, there are google links. Can we somehow copy the new benchmarks into
the yardstick repo?
>
> 21.08.2
s section explains how to register a template.
>
> On Mon, Aug 21, 2017 at 5:19 PM, Dmitriy Setrakyan wrote:
>
> > Prachi, is there an example for a template file? Is there an example of
> how
> > a template should be registered? Is there an example of how other
> extended
Denis, great progress.
At a first glance, I would suggest to move the page "What is Collocated
Processing" to Features and add some coding examples there.
Also, I am not sure if I agree with "Featured Solutions" page.
D.
P.S. don't forget to update sitemap.xml file.
On Mon, Aug 21, 2017 at 5:3
d Ignite from Java API, without any
XML. What will be saved? To prevent this ambiguity, I think the cleanest
way is to ask user to save the configuration to a file explicitly.
Makes sense?
> On Tue, Aug 22, 2017 at 6:52 AM, Dmitriy Setrakyan
> wrote:
>
> > On Mon, Aug 21,
is documented here -
> https://apacheignite.readme.io/docs/distributed-ddl#
> section-extended-parameters
>
> I've added a brief explanation on the SQL page (on the website) as well.
>
> On Mon, Aug 21, 2017 at 4:40 PM, Dmitriy Setrakyan wrote:
>
> > Nikita,
> >
On Mon, Aug 21, 2017 at 9:01 AM, Yakov Zhdanov wrote:
> Guys,
>
> I was asked how effectively change many rows in cache many times.
> Currently, this can done via ScanQuery - we send affinityCall(), inside
> callable we iterate over local primary cache partitions, filter entries by
> predicate an
y be set directly from code. What is wrong with persisting when user
explicitly calls saveToFile method?
>
> On Mon, Aug 21, 2017 at 5:22 PM, Dmitriy Setrakyan
> wrote:
>
> > On Mon, Aug 21, 2017 at 7:15 AM, Alexey Dmitriev >
> > wrote:
> >
> > > I wou
Nikita,
Thanks for checking. No, this is not on purpose.
Denis, do we have the template syntax documented anywhere?
D.
On Mon, Aug 21, 2017 at 9:42 AM, Nikita Ivanov wrote:
> I looked briefly and I couldn't find any explanation on "template" at all -
> the only unique caveat apart from standa
Completely agree. Why do we have Visor CLI join the cluster at all? It
should be issuing REST requests to the cluster remotely. Essentially, every
command should be a REST request/response.
Is this possible?
D.
On Mon, Aug 21, 2017 at 12:25 PM, Denis Magda wrote:
> Igniters,
>
> I would propos
Igniters,
There has been lots of talk of proposals about various usage metrics for
Ignite and nothing came of it. I would like to resurrect the topic and
propose something very simple and non-intrusive.
1. Update Checker
The main purpose of the update checker is not to collect metrics, but to
not
+1
On Mon, Aug 21, 2017 at 11:44 AM, Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> +1
>
> -Val
>
> On Mon, Aug 21, 2017 at 9:06 AM, Yakov Zhdanov
> wrote:
>
> > Guys,
> >
> > Currently to stop node on a particular server (not using visor or web
> > console) I need to run "jps" an
I like this better. We should give user an ability to save the updated
configuration into a file.
>
> On Mon, Aug 21, 2017 at 5:22 PM, Dmitriy Setrakyan
> wrote:
>
> > On Mon, Aug 21, 2017 at 7:15 AM, Alexey Dmitriev >
> > wrote:
> >
> > > I would sa
think how our configuration system should be
> changed to make it more obvious.
>
But in that case, what to do with XML configuration? Should it be updated
as well? Or even worse, what if user added configuration from code?
On Mon, Aug 21, 2017 at 5:11 PM, Dmitriy Setrakyan
> wrote:
&g
Igniters,
We should either update this repository or delete it. Why have a repository
with outdated benchmarks.
Thoughts?
D.
On Mon, Aug 21, 2017 at 7:14 AM, Aleksei Zaitsev
wrote:
> Thanks, looks like that's what I need.
>
> 21.08.2017, 12:17, "Nikolai Tikhonov" :
> > Hello,
> >
> > Yes, thi
I think the main question I have is whether this configuration change will
survive restarts. Part of me says it should, and the other part says it
shouldn't.
Does anyone have a strong opinion about this?
D.
On Mon, Aug 21, 2017 at 7:07 AM, Alexey Dmitriev
wrote:
> It looks like very useful and
On Fri, Aug 18, 2017 at 1:57 AM, Yakov Zhdanov wrote:
> Here is the list of params that can be changed - https://cwiki.apache.org/
> confluence/display/IGNITE/Allow+Configuration+Settings+Change+At+Runtime
>
> >No, the Ignite configuration is what Ignite receives on startup. Runtime
> >changes ar
I still do not see why anyone would explicitly call these 2 methods:
*Ignite::activation::establishBaselineTopology();*
*Ignite::activation::establishBaselineTopology(BaselineTopology bltTop);*
For example, if a web console, or some other admin process, want to
automatically set currently started
I don't see any list on the left. It takes me directly to the ticket.
On Fri, Aug 18, 2017 at 1:57 PM, Denis Magda wrote:
> You should see the list to the left. IGNITE-6116 will be shown as the
> first one.
>
> —
> Denis
>
> > On Aug 18, 2017, at 1:52 P
This link took me to this ticket directly:
https://issues.apache.org/jira/browse/IGNITE-6116
On Fri, Aug 18, 2017 at 1:42 PM, Denis Magda wrote:
> Can not share the filter. That’s the query string to see the tickets:
>
> https://issues.apache.org/jira/browse/IGNITE-6116?jql=
> project%20%3D%20IG
> BR,
> Serge
>
>
> On Wed, 16 Aug 2017 at 03:46, Dmitriy Setrakyan
> wrote:
>
> > I like #1 if possible. Of course, if the LFS is empty, then the new
> default
> > should be 4k.
> >
> > On Tue, Aug 15, 2017 at 12:01 PM, Ivan Rakov
> > wrote:
and initialization on the server,
> then we could automatically cancel services that are already deployed in a
> batch.
>
> чт, 17 авг. 2017 г. в 8:34, Dmitriy Setrakyan :
>
> > On Wed, Aug 16, 2017 at 8:17 AM, Denis Mekhanikov >
> > wrote:
> >
> > > I&
On Thu, Aug 17, 2017 at 7:34 AM, Sergey Chugunov
wrote:
> Dmitriy,
>
> As automatic creation of Baseline Topology is just another use case about
> the whole concept, lets discuss it in this thread and forget about parallel
> one.
>
> *initialActivationNodes* for desired configuration of Baseline
On Thu, Aug 17, 2017 at 10:37 AM, Yakov Zhdanov wrote:
> >I don't like the idea of intermixing changeable properties with constant
> >ones in the configuration. Moreover, the standard configuration class is
> >local to the node, while changing the config properties at runtime may be
> a
> >distri
Denis, it will be helpful to also file a ticket on this.
On Thu, Aug 17, 2017 at 1:20 PM, Denis Magda wrote:
> Hi Igor,
>
> Could you spend some time walking through the doc and updating it
> considering the latest features and changes?
> https://apacheignite.readme.io/docs/quering-data <
> http
Agree. If we remove the exception though, we need to make sure to print out
the warning that the eviction policy will be ignored with Ignite native
persistence enabled.
On Thu, Aug 17, 2017 at 1:35 PM, Denis Magda wrote:
> Dmitriy,
>
> >> Developers,
> >>
> >> Let me bring this to your attention
wrote:
> >>
> >> I cannot open this url.
> >> It is working?
> >>
> >> On Thu, Aug 17, 2017 at 8:16 AM, Dmitriy Setrakyan <
> dsetrak...@apache.org>
> >> wrote:
> >>
> >>> Looks very cool!
> >>>
> >&
On Thu, Aug 17, 2017 at 1:47 PM, Yakov Zhdanov wrote:
> Denis, you are absolutely right. Iterating through millions of objects is
> indeed a very complex task. Ignite casts a secret spell instead.\
>
Well, Ignite should cast a secret spell and do it in parallel, across
multiple threads. This wil
ated
documentation into its own separate SQL section.
> —
> Denis
>
> > On Aug 16, 2017, at 6:06 PM, Dmitriy Setrakyan
> wrote:
> >
> > Denis,
> >
> > I agree with Val. I am OK with using DBeaver as an example, but the name
> of
> > the doc should
> IgniteServices#deployAsync method may fail with an exception instead of
> returning a future. Shouldn't we change this behavior to make async
> operations always return a future whose get() method would throw an
> exception?
>
Makes sense to me. I think throwing exception fro
On Wed, Aug 16, 2017 at 3:39 PM, Denis Magda wrote:
> Developers,
>
> Let me bring this to your attention. Why do we throw an exception if the
> user has both an eviction policy and the Ignite persistence configured? Why
> don’t we simply ignore the eviction policy printing a warning and proceed
Looks very cool!
My first comment is that the home page looks different in Windows Edge from
Mac. For example, the font of the "Memory-Centric Data Platform" is
different and bold is not visible in Windows.
D.
On Wed, Aug 16, 2017 at 4:30 PM, Denis Magda wrote:
> Igniters,
>
> Some of us have
aced one more issue that prevents us
> from
> >> using the bulk inserts:
> >> https://issues.apache.org/jira/browse/IGNITE-6092 <
> >> https://issues.apache.org/jira/browse/IGNITE-6092>
> >>
> >> *Alexander P.*, *Vladimir*, how difficult is to su
ding does not introduce any bugs, I would upgrade, so
we do not create version conflicts on user side.
>
> —
> Denis
>
> > On Aug 16, 2017, at 5:12 PM, Dmitriy Setrakyan
> wrote:
> >
> > On Wed, Aug 16, 2017 at 5:02 PM, Denis Magda wrote:
> >
> >> H
; —
> Denis
>
> > On Aug 16, 2017, at 10:36 AM, Alexey Kuznetsov
> wrote:
> >
> > Done
> >
> > https://issues.apache.org/jira/browse/IGNITE-6090
> >
> > On Wed, Aug 16, 2017 at 8:01 PM, Dmitriy Setrakyan <
> dsetrak...@apache.org>
>
The answer is Yes, we should update. Jira ticket assigned to the next
release should be enough in my view.
D.
On Wed, Aug 16, 2017 at 2:38 AM, Alexey Kuznetsov
wrote:
> Hi, All!
>
> Do we have any policy for updating third-party dependencies?
>
> For example, I found that we are using very old
> non-deterministic affinity functions, and distributed joins are not enabled
> 4) Fix FairAffinityFunction and make it deterministic, it should not depend
> on previous state.
>
> Makes sense?
>
> On Wed, Aug 16, 2017 at 3:31 AM, Dmitriy Setrakyan
> wrote:
>
> > On Tue,
e:
> > > >
> > > > > Dmitriy,
> > > > >
> > > > > Yes, you're right. Moreover, it looks like a good practice to
> combine
> > > > > caches that will be used for collocated JOINs in one group since it
> > > >
Yakov,
I don't like the idea of intermixing changeable properties with constant
ones in the configuration. Moreover, the standard configuration class is
local to the node, while changing the config properties at runtime may be a
distributed operation that needs to be propagated across the cluster.
I like #1 if possible. Of course, if the LFS is empty, then the new default
should be 4k.
On Tue, Aug 15, 2017 at 12:01 PM, Ivan Rakov wrote:
> Guys,
>
> We have benchmarked how checkpoint write speed on SSD disk depends on
> various parameters. It became absolutely obvious that using 4K pages i
good practice to combine
> > > caches that will be used for collocated JOINs in one group since it
> > reduces
> > > overall overhead.
> > >
> > > I think it's not a problem to add this restriction to the SQL JOIN
> level
> >
x27;t have a way to wait for the rest of the services to deploy.
> Maybe we should return some king of deployment result, containing a future
> along with a collection of failed services, instead of throwing an
> exception?
>
> пн, 14 авг. 2017 г. в 18:03, Dmitriy Setrakyan :
>
>
Added one more suggestion below. BTW, if there is no ticket, let's create
one and copy all the suggestions there.
On Tue, Aug 15, 2017 at 1:13 AM, Dmitriy Setrakyan
wrote:
> Guys,
>
> Where is the ticket for adding control.[sh|bat] script to the bin folder?
> I cannot find
Guys,
Where is the ticket for adding control.[sh|bat] script to the bin folder? I
cannot find any mention of it. Was there a discussion on the dev list?
Here are the issues I am seeing with the script:
1. It could be named better. Perhaps the name "cluster-ops" or
"cluster-switch" would be
Hi Denis, I agree, we should have an API for batch service deployment. My
comments are inline...
On Mon, Aug 14, 2017 at 2:22 AM, Denis Mekhanikov
wrote:
> Hi Igniters!
>
> Currently Ignite doesn't have support for batch service deployment, but it
> may be a very useful feature in case of a big
t require it.
- screenshot of configuring these properties with a popular SQL tool
>
> Best Regards,
> Igor
>
> On Sun, Aug 13, 2017 at 7:20 PM, Dmitriy Setrakyan
> wrote:
>
> > On Fri, Aug 11, 2017 at 7:31 PM, Denis Magda
> wrote:
> >
> > > Dmitriy,
> &g
standpoint.
> I would rather add a direct reference from JDBC/ODBC docs to Pentaho and
> Tablea.
>
> Denis
>
> On Friday, August 11, 2017, Dmitriy Setrakyan
> wrote:
>
> > Igniters,
> >
> > I have tried to connect to Ignite from DBeaver [1], and realized t
I still don't understand per-partition compression, which is only local.
How do entries get updated in the middle of a partition file?
D.
On Fri, Aug 11, 2017 at 3:44 AM, Yakov Zhdanov wrote:
> Ivan, your points definitely make sense, however, I see at list one issue
> compared to per-page appr
g down "node set" road:
> >
> > -fixed node set
> > -established node set
> > -base node set
> >
> > On Thu, Aug 10, 2017 at 5:23 PM, Dmitriy Setrakyan <
> dsetrak...@apache.org>
> > wrote:
> >
> >> Can we brainstorm on the
I would call the setter setBaselineTopology, without the word Descriptor.
Also, perhaps this BaselineTopology should be a standard predicate, just
like the Node Filter we already have for ClusterGroup, so users could
provide a custom cluster initialization logic. We, of course, should
provide a de
Igniters,
I have tried to connect to Ignite from DBeaver [1], and realized that there
are some usability issues we need to address before the next release:
1. We need to have documentation on how to configure JDBC and ODBC
drivers with external SQL tools [2]
2. You cannot highlight multi
Dmitriy Setrakyan created IGNITE-6048:
-
Summary: Need to document how to connect to Ignite from external
SQL tools
Key: IGNITE-6048
URL: https://issues.apache.org/jira/browse/IGNITE-6048
Project
Dmitriy Setrakyan created IGNITE-6047:
-
Summary: Need to support "show" SQL commands
Key: IGNITE-6047
URL: https://issues.apache.org/jira/browse/IGNITE-6047
Project: Ignite
Dmitriy Setrakyan created IGNITE-6046:
-
Summary: Multiple SQL statements in one command do not work
Key: IGNITE-6046
URL: https://issues.apache.org/jira/browse/IGNITE-6046
Project: Ignite
Igniters,
I have reviewed the Ignite integrations page, and it looks like most
integrations are stuck on 1.9 version:
https://cwiki.apache.org/confluence/display/IGNITE/External+Integrations
We should upgrade them to the latest release.
Andrey Gura, can you please comment?
D.
o use
> Ignite with Hibernate this way, so we need to do some testing first to
> identify limitations/issues we have there.
>
> -Val
>
> On Wed, Aug 9, 2017 at 12:58 PM, Dmitriy Setrakyan
> wrote:
>
> > Igniters,
> >
> > Given that we have a very rich S
Dmitriy Setrakyan created IGNITE-6045:
-
Summary: Hibernate dialect for Ignite
Key: IGNITE-6045
URL: https://issues.apache.org/jira/browse/IGNITE-6045
Project: Ignite
Issue Type: Wish
Yakov,
I like the idea, but I am not sure how we will separate properties that are
dynamically changeable from the constant ones.
Also, what is the API for updating these properties? Perhaps we can create
a special interface, e.g. IgniteConfigurationRuntime (similar to Java
Runtime class), which
On Fri, Aug 11, 2017 at 10:38 AM, Akmal Chaudhri <
akmal.chaud...@gridgain.com> wrote:
> Dimitriy,
>
> I will take a look at those and pick-up the documentation tickets early
> next week.
>
>
Awesome! Feel free to assign any tickets to yourself.
> Thanks.
>
> On
Igniters,
I have filed several website tickets to reflect the addition of persistence
in the latest 2.1 release:
https://issues.apache.org/jira/browse/IGNITE-6036
https://issues.apache.org/jira/browse/IGNITE-6037
https://issues.apache.org/jira/browse/IGNITE-6038
https://issues.apache.org/jira/bro
Dmitriy Setrakyan created IGNITE-6041:
-
Summary: Update Gettting Started documentation page
Key: IGNITE-6041
URL: https://issues.apache.org/jira/browse/IGNITE-6041
Project: Ignite
Issue
Dmitriy Setrakyan created IGNITE-6040:
-
Summary: Update Distributed SQL Database page on the website
Key: IGNITE-6040
URL: https://issues.apache.org/jira/browse/IGNITE-6040
Project: Ignite
Dmitriy Setrakyan created IGNITE-6039:
-
Summary: Update Persistence page on the website
Key: IGNITE-6039
URL: https://issues.apache.org/jira/browse/IGNITE-6039
Project: Ignite
Issue Type
Dmitriy Setrakyan created IGNITE-6038:
-
Summary: Update Data Grid page on teh website to reflect
Persistence
Key: IGNITE-6038
URL: https://issues.apache.org/jira/browse/IGNITE-6038
Project
Dmitriy Setrakyan created IGNITE-6037:
-
Summary: Ignite 2.1 features overview changes on the website
Key: IGNITE-6037
URL: https://issues.apache.org/jira/browse/IGNITE-6037
Project: Ignite
Dmitriy Setrakyan created IGNITE-6036:
-
Summary: Ignite 2.1 use case changes on the website
Key: IGNITE-6036
URL: https://issues.apache.org/jira/browse/IGNITE-6036
Project: Ignite
Issue
Can we brainstorm on the names again, I am not sure we have a consensus on
the name "baseline topology". This will be included in Ignite
configuration, so the name has to be clear.
Some of the proposals were:
- baseline topology
- minimal node set
- node restart set
- minimal topology
Any other
Igniters,
Given that we have a very rich SQL support starting with version 2.1, does
it make sense to create an Ignite SQL dialect for Hibernate?
https://docs.jboss.org/hibernate/orm/3.6/reference/en-US/html/session-configuration.html#configuration-optional-dialects
D.
Vova,
I do not understand how (2) will help us reduce the size of the serialized
object. It sounds like we need to serialize an object the way we do today,
and then compress it when it arrives to the server side and gets stored in
some page. This looks like a double whammy.
I do not understand wh
On Wed, Aug 9, 2017 at 6:28 AM, ezhuravl wrote:
> Folks,
>
> I've started working on a https://issues.apache.org/
> jira/browse/IGNITE-5836
> ticket and found that the recently added feature with cacheGroups doing
> pretty much the same that was described in this issue. CacheGroup
> guarantees
>
On Wed, Aug 9, 2017 at 5:32 AM, Николай Ижиков
wrote:
> Vladimir,
>
> As far as I can understand behaviour of U.currentTimeMillis() breaks
> transaction timeout test:
>
So, if you change the call to System.currentTimeMillis(), the test passes?
On Wed, Aug 9, 2017 at 4:59 AM, Николай Ижиков
wrote:
> Vladimir,
>
> > There is nothing wrong with U.currentTimeMillis() at the
> moment.
>
> I think we can't rely on the return value for time measurement.
> Is it true? Is it OK for you?
>
> It very counterintuitive for me as newcomer.
>
I agre
I have tried to send a google invite to the dev list. Never done it before,
so let's see if it works.
D.
On Tue, Aug 8, 2017 at 9:13 AM, Konstantin Boudnik wrote:
> A reminder to register for the webinar if you're interested.
> --
> With regards,
> Konstantin (Cos) Boudnik
> 2CAC 8312 4870 D8
...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
TRUE;CN=dev@ignite.apache.org;X-NUM-GUESTS=0:mailto:dev@ignite.apache.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
;CN=Dmitriy Setrakyan;X-NUM-GUESTS=0:mailto:dsetrak...@gridgain.com
mplemented just because no one has ever implemented
> them.
>
> Best Regards,
> Igor
>
> On Fri, Aug 4, 2017 at 9:32 PM, Dmitriy Setrakyan
> wrote:
>
> > Nice!
> >
> > I am not sure I like the name "conformance" however. How about renaming
>
about Data Frame support for longer than
a year. I think we should advise our users to switch to JDBC until the
community gets someone to implement it.
>
> -Val
>
> On Thu, Aug 3, 2017 at 12:12 AM, Dmitriy Setrakyan
> wrote:
>
> > On Thu, Aug 3, 2017 at 9:04 AM, Jörn Frank
I was asleep and woke up in cold sweat realizing that I don't have the
login to TC. How do I get one?
On Fri, Aug 4, 2017 at 10:53 PM, Aleksey Chetaev
wrote:
> If anyone can’t sleep at night
> If anyone sleep very bad
> If you afraid that your password
> Can evil hacker steal right now
>
> For t
Nice!
I am not sure I like the name "conformance" however. How about renaming it
to "specification"?
Also, would be nice to get a sense about why certain features are
unsupported and what are the plans to get closer to 100% compliance?
D.
On Fri, Aug 4, 2017 at 1:08 PM, Vladimir Ozerov
wrote:
than
> JDBC would be more beneficial.
>
Jorn, I completely agree. However, we have not been able to find a
contributor for this feature. You sound like you have sufficient domain
expertise in Spark and Ignite. Would you be willing to help out?
> > On 3. Aug 2017, at 08:57, Dmitriy Setrakya
larger data
volumes and supports data pagination automatically.
> > On 3. Aug 2017, at 08:17, Dmitriy Setrakyan
> wrote:
> >
> > Jorn, thanks for your feedback!
> >
> > Can you explain how the direct support would be different from the JDBC
> > support?
>
interactive analysis or different
> Spark applications sharing data.
>
> > On 3. Aug 2017, at 05:12, Dmitriy Setrakyan
> wrote:
> >
> > Igniters,
> >
> > We have had the integration with Spark Data Frames on our roadmap for a
> > while:
> >
Igniters,
We have had the integration with Spark Data Frames on our roadmap for a
while:
https://issues.apache.org/jira/browse/IGNITE-3084
However, while browsing Spark documentation, I cam across the generic JDBC
data frame support in Spark:
https://spark.apache.org/docs/latest/sql-programming-g
First of all, this sounds a bit too scientific and will likely be
misunderstood and misused. Is there a chance to give it a better name and a
simpler use case and description?
Secondly, I do agree that it should be mandatory to update the BT. For
example, what if I want to add several nodes to the
Let us not forget that the main purpose of such protocol is to enable other
users contribute their own client implementations for various languages.
Also, most JDBC and ODBC use cases work in thread-per-connection mode.
I think that if we introduce a multi-threaded client here, then it will be
a l
mmands for our own parser?
> > >
> > > - Alex
> > >
> > > 2017-08-02 9:01 GMT+03:00 Vladimir Ozerov :
> > > > No, it will work as follows:
> > > >
> > > > Model parse(String sql) {
> > > > Model res = tryP
. But that’s about too massive preloading and not
> > >> caused
> > >>>> by the ability of the legacy off-heap memory to grow infinitely. The
> > >> same
> > >>>> preloading would cause a hang if the Java heap memory mode is used.
> > >>>>
> > >&
Agree with Denis. I think that we should treat it as a starting point for
the release notes, and further update it before releases.
On Wed, Aug 2, 2017 at 10:58 PM, Denis Magda wrote:
> Guys,
>
> We're on the same page that the page has to look more colorful and
> informative. This is exactly wh
We have to wait with any default changes to 3.0, unfortunately.
On Wed, Aug 2, 2017 at 8:30 PM, Vladimir Ozerov
wrote:
> Not sure about readFromBackup, but changing PRIMARY_SYNC to FULL_SYNC looks
> safe to me. Any other thoughts?
>
> ср, 2 авг. 2017 г. в 21:10, Denis Magda :
>
> > +1 for both s
s the reason?
>
> The very problem is that before being started once on production
> environment, Ignite will typically be started hundred times on developer's
> environment. I think that default should be ~10% of total RAM.
>
Why not 80% of *free *RAM?
>
> On Wed, Aug
On Wed, Aug 2, 2017 at 7:27 AM, Vladimir Ozerov
wrote:
> Please see original Sergey's message - when persistence is enabled, memory
> is not allocated incrementally, maxSize is used.
>
Why?
> Default settings must allow for normal work on developer's environment.
>
Agree, but why not in incre
How about allowing 8 bytes of extra space for any user-specific additional
data? For example, I can see that some implementations of this protocol
will need to pass some extra parameters to the server. Of course, in that
case the server side protocol handler should have a hook to react to these
ext
On Tue, Aug 1, 2017 at 11:08 PM, Vladimir Ozerov
wrote:
> Own parser capable of processing non-SELECT and non-DML statements.
>
And how will it integrate with H2 parser? Or are you suggesting that we get
rid of H2 SQL parser?
>
> On Tue, Aug 1, 2017 at 9:44 PM, wrote:
>
> > Vova, I am not sur
Is the final design documented in the ticket?
On Sat, Jul 29, 2017 at 5:04 AM, Alexei Scherbakov <
alexey.scherbak...@gmail.com> wrote:
> Anton,
>
> I'm fine with proposed solution using AffinityComputeTask.
>
> Please take care of issues pointed by me while implementing.
>
> Each job should some
a complicated and expensive solution - looking up string
> format somewhere in the metadata will be slow.
>
> "encoded string" data type suggestion from Vladimir looks better to me from
> performance and implementation standpoint.
>
> Thanks,
> Pavel
>
>
>
> On
ds,
> Igor
>
> On Wed, Jul 26, 2017 at 7:22 PM, Dmitriy Setrakyan
> wrote:
>
> > On Wed, Jul 26, 2017 at 3:40 AM, Vyacheslav Daradur >
> > wrote:
> >
> > >
> > > > Encoding must be set on per field basis. This will give us as most
> &
On Thu, Jul 27, 2017 at 10:51 AM, Dmitriy Setrakyan >
> wrote:
>
> > Sergey, why not prohibit any reuse of the builder and throw exception
> right
> > away?
> >
> > On Wed, Jul 26, 2017 at 6:20 AM, Sergey Chugunov <
> > sergey.chugu...@gmail.com>
&g
Sergey, why not prohibit any reuse of the builder and throw exception right
away?
On Wed, Jul 26, 2017 at 6:20 AM, Sergey Chugunov
wrote:
> Hello folks,
>
> Recently I filed a ticket [1] with very simple test where correct usage of
> BinaryObjectBuilder is vague.
>
> The issue boils down to the
On Wed, Jul 26, 2017 at 3:40 AM, Vyacheslav Daradur
wrote:
>
> > Encoding must be set on per field basis. This will give us as most
> flexible
> > solution at the cost of 1-byte overhead.
>
> > Vova, I agree that the encoding should be set on per-field basis, but at
> > the table level, not at a
701 - 800 of 2105 matches
Mail list logo
