Re: Updated libs for ignite-hibernate_4.2

[Denis Magda]

Hi Earle,

As I can see ignite-hibernate_4.2 already uses the latest stable version of
Hibernate 4.2:


org.hibernate
hibernate-core
4.2.21.Final



What's your version of Hibernate? Are you suggesting to support Hibernate
5.4?

Just in case, there is a version of the integration for Hibernate 5.1 and
5.3. You need to use ignite-hibernate_5.1 and ignite-hibernate_5.3
artifacts for those.

-
Denis


On Thu, Jun 11, 2020 at 11:24 AM Earle Nietzel 
wrote:

> Hello,
>
> I apologize for posting this here but was noticing that the maven lib
>   
> org.apache.ignite
> ignite-hibernate_4.2
> ${ignite.version}
>   
>
> hasn't been updated in a while is there by any chance someone here might be
> able to nudge someone to release some updated libs.
>
> The last version was
> ignite-hibernate_4.2-2.7.2.jar Wed Feb 06 14:17:29 MST 2019
> would like to get a 2.8.1 if possible?
>
> Thanks,
> -earle
>

Updated libs for ignite-hibernate_4.2

[Earle Nietzel]

Hello,

I apologize for posting this here but was noticing that the maven lib
  
org.apache.ignite
ignite-hibernate_4.2
${ignite.version}
  

hasn't been updated in a while is there by any chance someone here might be
able to nudge someone to release some updated libs.

The last version was
ignite-hibernate_4.2-2.7.2.jar Wed Feb 06 14:17:29 MST 2019
would like to get a 2.8.1 if possible?

Thanks,
-earle

[jira] [Created] (IGNITE-13147) Avoid DHT topology updates before it's initialization

[Alexey Scherbakov (Jira)]

Alexey Scherbakov created IGNITE-13147:
--

 Summary: Avoid DHT topology updates before it's initialization
 Key: IGNITE-13147
 URL: https://issues.apache.org/jira/browse/IGNITE-13147
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.8
Reporter: Alexey Scherbakov
 Fix For: 2.9


It can happen if a partition state is restored from persistent store on logical 
recovery and can cause NPE on older versions during illegal access to 
unitialized topology:
{noformat}
[ERROR][exchange-worker-#41][GridDhtPartitionsExchangeFuture] Failed to 
reinitialize local partitions (rebalancing will be stopped): 
GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=102, 
minorTopVer=0], discoEvt=DiscoveryEvent [evtNode=TcpDiscoveryNode 
[id=d159da1c-6f70-4ef2-bfa4-4feb64b829de, consistentId=T1SivatheObserver, 
addrs=ArrayList [10.44.166.91, 127.0.0.1], sockAddrs=HashSet [/127.0.0.1:56500, 
clrv052580.ic.ing.net/10.44.166.91:56500], discPort=56500, order=102, 
intOrder=60, lastExchangeTime=1586354937705, loc=true,, isClient=false], 
topVer=102, msgTemplate=null, nodeId8=d159da1c, msg=null, type=NODE_JOINED, 
tstamp=1586354901638], nodeId=d159da1c, evt=NODE_JOINED]
java.lang.NullPointerException: null
at 
org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentV2.getIds(GridAffinityAssignmentV2.java:211)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.topology.GridDhtPartitionTopologyImpl.updateLocal(GridDhtPartitionTopologyImpl.java:2554)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.topology.GridDhtPartitionTopologyImpl.afterStateRestored(GridDhtPartitionTopologyImpl.java:714)
at 
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.lambda$beforeExchange$38edadb$1(GridCacheDatabaseSharedManager.java:1514)
at 
org.apache.ignite.internal.util.IgniteUtils.lambda$null$1(IgniteUtils.java:10790)
at java.util.concurrent.FutureTask.run(Unknown Source) ~[?:1.8.0_241]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) 
~[?:1.8.0_241]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) 
~[?:1.8.0_241]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_241]
{noformat}



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

Re: IGNITE-12952 Enable travis ci for ignite-extensions

[Maxim Muzafarov]

Saikat,


Please, take a look at and INFRA ticket for enabling Travis
configuration for Apache Ignite project. Seems you need to create
something similar.
https://issues.apache.org/jira/browse/INFRA-20126



On Thu, 11 Jun 2020 at 03:25, Saikat Maitra  wrote:
>
> Hi Maxim, Pavel
>
> Can you please share more info about how travis build was enabled for
> ignite repo?
>
> I tried to execute the travis CI build for ignite-extensions but I do not
> have sufficient access to enable the travis build for ignite-extensions
> repo.
>
> Regards,
> Saikat
>
>
> On Sun, May 31, 2020 at 4:18 PM Saikat Maitra 
> wrote:
>
> > Hi,
> >
> > I have raised a PR to enable travis CI build.
> >
> > Jira : https://issues.apache.org/jira/browse/IGNITE-12952
> >
> > PR : https://github.com/apache/ignite-extensions/pull/15
> >
> > I need more info about how travis build was enabled for ignite repo. I
> > tried to execute the travis CI build for ignite-extensions but I do not
> > have sufficient access to enable the travis build for ignite-extensions
> > repo.
> >
> > https://travis-ci.org/github/apache/ignite-extensions
> >
> > Regards,
> > Saikat
> >
> >

Re: Can I get write permissions for Apache Wiki?

[Ilya Kasnacheev]

Hello!

Write permissions granted.

Regards,
-- 
Ilya Kasnacheev


чт, 11 июн. 2020 г. в 10:14, Данилов Семён :

> Hello!
>
> It's sdanilov
>
> Regards,
> Semyon Danilov
>
> 09.06.2020, 13:04, "Ilya Kasnacheev" :
> > Hello!
> >
> > What is your login for apache wiki?
> >
> > Regards,
> > --
> > Ilya Kasnacheev
> >
> > вт, 9 июн. 2020 г. в 10:11, Данилов Семён :
> >
> >>  ello Igniters,
> >>
> >>  I’m planning to change
> >>
> https://cwiki.apache.org/confluence/display/IGNITE/Ignite+Persistent+Store+-+under+the+hood
> >>  (because I have pending pull request for changing binary meta
> location),
> >>  but don’t have rights for this.
> >>  Can someone please give me the access?
> >>
> >>  Sincerely yours,
> >>  Semyon Danilov.
>

[jira] [Created] (IGNITE-13146) OpenCensus example does not work from release build

[Ilya Kasnacheev (Jira)]

Ilya Kasnacheev created IGNITE-13146:


 Summary: OpenCensus example does not work from release build
 Key: IGNITE-13146
 URL: https://issues.apache.org/jira/browse/IGNITE-13146
 Project: Ignite
  Issue Type: Bug
  Components: build
Affects Versions: 2.9
Reporter: Ilya Kasnacheev
Assignee: Nikolay Izhikov
 Fix For: 2.9


This happens in a binary distribution of 2.9:

{code}
/Downloads/apache-ignite-slim-2.9.0-SNAPSHOT-bin/examples% mvn clean install
[INFO] 
[INFO] -< org.apache.ignite:ignite-examples >--
[INFO] Building ignite-examples 2.9.0-SNAPSHOT
[INFO] [ jar ]-
...
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ 
ignite-examples ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 255 source files to 
/home/gridgain/Downloads/apache-ignite-slim-2.9.0-SNAPSHOT-bin/examples/target/classes
...
[INFO] -
[ERROR] COMPILATION ERROR : 
[INFO] -
[ERROR] 
/home/gridgain/Downloads/apache-ignite-slim-2.9.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/opencensus/OpenCensusMetricsExporterExample.java:[20,47]
 package io.opencensus.exporter.stats.prometheus does not exist
[ERROR] 
/home/gridgain/Downloads/apache-ignite-slim-2.9.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/opencensus/OpenCensusMetricsExporterExample.java:[21,37]
 package io.prometheus.client.exporter does not exist
[ERROR] 
/home/gridgain/Downloads/apache-ignite-slim-2.9.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/opencensus/OpenCensusMetricsExporterExample.java:[34,47]
 package org.apache.ignite.spi.metric.opencensus does not exist
[ERROR] 
/home/gridgain/Downloads/apache-ignite-slim-2.9.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/opencensus/OpenCensusMetricsExporterExample.java:[54,9]
 cannot find symbol
  symbol:   variable PrometheusStatsCollector
  location: class 
org.apache.ignite.examples.opencensus.OpenCensusMetricsExporterExample
[ERROR] 
/home/gridgain/Downloads/apache-ignite-slim-2.9.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/opencensus/OpenCensusMetricsExporterExample.java:[57,9]
 cannot find symbol
  symbol:   class HTTPServer
  location: class 
org.apache.ignite.examples.opencensus.OpenCensusMetricsExporterExample
[ERROR] 
/home/gridgain/Downloads/apache-ignite-slim-2.9.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/opencensus/OpenCensusMetricsExporterExample.java:[57,30]
 cannot find symbol
  symbol:   class HTTPServer
  location: class 
org.apache.ignite.examples.opencensus.OpenCensusMetricsExporterExample
[ERROR] 
/home/gridgain/Downloads/apache-ignite-slim-2.9.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/opencensus/OpenCensusMetricsExporterExample.java:[62,9]
 cannot find symbol
  symbol:   class OpenCensusMetricExporterSpi
  location: class 
org.apache.ignite.examples.opencensus.OpenCensusMetricsExporterExample
[ERROR] 
/home/gridgain/Downloads/apache-ignite-slim-2.9.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/opencensus/OpenCensusMetricsExporterExample.java:[62,71]
 cannot find symbol
  symbol:   class OpenCensusMetricExporterSpi
  location: class 
org.apache.ignite.examples.opencensus.OpenCensusMetricsExporterExample
[INFO] 8 errors 
[INFO] -
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
{code}

This is because pom-standalone.xml and pom-standalone-lgpl.xml files needs to 
be updated in accordance with examples/pom.xml changes. This is currently a 
blocker for 2.9.



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

[jira] [Created] (IGNITE-13145) NPE on node stop can cause JVM halt with default failure handler

[Aleksey Plekhanov (Jira)]

Aleksey Plekhanov created IGNITE-13145:
--

 Summary: NPE on node stop can cause JVM halt with default failure 
handler
 Key: IGNITE-13145
 URL: https://issues.apache.org/jira/browse/IGNITE-13145
 Project: Ignite
  Issue Type: Bug
Reporter: Aleksey Plekhanov
Assignee: Aleksey Plekhanov


{{TcpCommunicationSpi}} have injected {{@IgniteLogger}} resource.  
{{TcpCommunicationSpi.sendMessage0}} tries to access this resource without null 
check, but when the node is stopping injected resources are cleaned up. If some 
threads are trying to send something via communication SPI on stopping node, 
NPE is thrown with subsequent failure handler call and JVM halt with default 
failure handler. This is undesirable when Ignite is running in embedded mode 
since all other JVM applications will be stopped.

Error stack:
{noformat}
[11:34:39,194][SEVERE][sys-stripe-11-#8570%280332bb-89f3-4227-9d14-c319bbf3ca0c%][]
 Critical system error detected. Will be handled accordingly to configured 
handler [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0, 
super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet 
[SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], 
failureCtx=FailureContext [type=SYSTEM_WORKER_TERMINATION, 
err=java.lang.NullPointerException]]
java.lang.NullPointerException
at 
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage0(TcpCommunicationSpi.java:2898)
at 
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage(TcpCommunicationSpi.java:2882)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:2035)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.sendToGridTopic(GridIoManager.java:2132)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1257)
at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:1296)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.sendDeferredUpdateResponse(GridDhtAtomicCache.java:3643)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$DeferredUpdateTimeout.run(GridDhtAtomicCache.java:3889)
at 
org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:565)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.base/java.lang.Thread.run(Thread.java:834)
[11:34:39,214][SEVERE][sys-stripe-11-#8570%280332bb-89f3-4227-9d14-c319bbf3ca0c%][]
 JVM will be halted immediately due to the failure: [failureCtx=FailureContext 
[type=SYSTEM_WORKER_TERMINATION, err=java.lang.NullPointerException]]{noformat}
 This problem occurs often on team-city in "Java thin client" suite 
(ReliabilityTest#testFailover).



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

Re: Tool for performance statistics reports

[Nikita Amelchev]

Hello,

> Can you please share more info on how we can use the profiling tool with
> ignite-extensions modules?

I have updated the module readme file. You can find instructions
there. For now, I am working on review fixes and marked PR as a draft.

чт, 11 июн. 2020 г. в 03:21, Saikat Maitra :
>
> Hello Nikita,
>
> I observed we have an open PR in ignite repo for this feature with
> different set of changes compared to ignite extensions repo.
>
>
> apache/ignite#7693 
>
> https://github.com/apache/ignite-extensions/pull/16
>
> Can you please share more info on how we can use the profiling tool with
> ignite-extensions modules?
>
>
> Regards,
>
> Saikat
>
> On Mon, Jun 8, 2020 at 5:51 AM Nikolay Izhikov  wrote:
>
> > Hello, Alexey.
> >
> > Thanks for the review.
> >
> > My understanding if the following:
> >
> > We will have 3 in-depth tool to find issues in cluster:
> >
> > 1. Metrics + System views - data that describe Ignite entities very
> > high-level.
> >
> > 2. Profiling - tool to know what specific query of transactions are slow.
> > In many cases, this knowledge is enough to fix the issue(rewrite query,
> > redesign transactions flow, etc)
> >
> > 3. Tracing - tool to know why one of 1000 of the same queries was slow.
> > The most detailed view of the Ignite internal processes.
> >
> > > For example, a user would not be able to match a long task with a long
> > job in that task.
> >
> > This is not true.
> > Profiling report will aggregate data from all nodes.
> > So there will be both
> >
> >  * summary time of the task
> >  * time of the each job in the task.
> >
> >
> > > 8 июня 2020 г., в 12:52, Alexey Goncharuk 
> > написал(а):
> > >
> > > Nikita, Igniters,
> > >
> > > I left a few comments on the tool itself in the PR.
> > >
> > > However, I would like to reiterate and discuss why a user would prefer to
> > > use the profiling tool over tracing? Profiling tool only captures very
> > > high-level details of the operations (a single cache operation, for
> > > example), and does not interconnect operations happened on different
> > nodes.
> > > For example, a user would not be able to match a long task with a long
> > job
> > > in that task. In other words, profiling data is always a subset of data
> > > collected by tracing.
> > >
> > > Maybe it makes sense to adopt local log file approach to write spans so
> > we
> > > can process those spans later to build a report?
> > >
> > > чт, 4 июн. 2020 г. в 11:16, Nikita Amelchev :
> > >
> > >> Hi, Igniters.
> > >>
> > >> I have implemented cluster profiling and tool to build the performance
> > >> report. It's ready to be reviewed. [1, 2]
> > >>
> > >> Profiling can be managed by JMX bean. I have plans to implement it to
> > >> control.sh also.
> > >>
> > >> Nodes write statistics to the temporary off heap buffer and then one
> > >> thread flushes to the profiling files. The write mechanics and format
> > >> is like WAL logging.
> > >> The report contains the following statistics:
> > >> - nodes and caches info
> > >> - cache operations and transaction statistics
> > >> - SQL and scan queries statistics (include logical and physical reads
> > per
> > >> query)
> > >> - tasks and jobs statistics.
> > >>
> > >> More details in the IEP [3].
> > >>
> > >> [1] https://github.com/apache/ignite/pull/7693
> > >> [2] https://issues.apache.org/jira/browse/IGNITE-12666
> > >> [3]
> > >>
> > https://cwiki.apache.org/confluence/display/IGNITE/Cluster+performance+profiling+tool
> > >>
> > >> вс, 26 апр. 2020 г. в 17:29, Вячеслав Коптилин <
> > slava.kopti...@gmail.com>:
> > >>>
> > >>> Hello Nikolay,
> > >>>
> >  Who deprecated visor and when? Maybe I miss something?
> > >>> On the one hand, there was technically no community consensus that this
> > >>> tool should be obsolete.
> > >>> On the other hand, my opinion based on the following topic:
> > >>>
> > >>
> > http://apache-ignite-developers.2346864.n4.nabble.com/Re-Visor-plugin-tp44879p44939.html
> > >>> Moreover, it seems to me, currently, the control utility is widely used
> > >> and
> > >>> actively developed, instead of the visor.
> > >>>
> >  It's true that, for now, Ignite doesn't have "tool strategy" I think
> > >> it's
> > >>> a big issue from the user's point of view.
> > >>> I absolutely agree with that.
> > >>>
> >  We should solve it in the nearest time. Feel free to start this
> > >> activity
> > >>> I have no plan at the moment. However, at the first stage, we could
> > >>> understand the difference between visor and control utility.
> > >>> All useful features from visor should be moved/implemented in control
> > >>> utility and after that visor tool and should be marked as
> > >>> deprecated/obsoleted.
> > >>>
> >  You need to throw in control.sh also, which does some kind of
> > >> statistics
> > >>> too, such as idle_verify.
> >  Please, clarify your idea:
> >    We should use some info from control.sh to the report?
> > 

Re: [MTCGA]: new failures in builds [5376278] needs to be handled

[Alex Plehanov]

Caused by my fix [1]. Ticket created [2], in progress.

[1]: https://issues.apache.org/jira/browse/IGNITE-13096
[2]: https://issues.apache.org/jira/browse/IGNITE-13135

ср, 10 июн. 2020 г. в 23:01, :

> Hi Igniters,
>
>  I've detected some new issue on TeamCity to be handled. You are more than
> welcomed to help.
>
>  If your changes can lead to this failure(s): We're grateful that you were
> a volunteer to make the contribution to this project, but things change and
> you may no longer be able to finalize your contribution.
>  Could you respond to this email and indicate if you wish to continue and
> fix test failures or step down and some committer may revert you commit.
>
>  *New test failure in master
> CacheRegisterMetadataLocallyTest.testClientFindsValueByAffinityKeyDynamicCacheWithoutExtraRequest
>
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-5293904454158188493=%3Cdefault%3E=testDetails
>
>  *New test failure in master
> CacheRegisterMetadataLocallyTest.testClientFindsValueByAffinityKeyStaticCacheWithoutExtraRequest
>
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-5649732816476371550=%3Cdefault%3E=testDetails
>  Changes may lead to failure were done by
>  - ravil galeyev 
> https://ci.ignite.apache.org/viewModification.html?modId=902925
>  - ktkalenko 
> https://ci.ignite.apache.org/viewModification.html?modId=902844
>  - ilya kasnacheev 
> https://ci.ignite.apache.org/viewModification.html?modId=902841
>  - vladsz83 
> https://ci.ignite.apache.org/viewModification.html?modId=902920
>  - ilya kasnacheev 
> https://ci.ignite.apache.org/viewModification.html?modId=902843
>  - pavel tupitsyn 
> https://ci.ignite.apache.org/viewModification.html?modId=902890
>  - aleksey plekhanov 
> https://ci.ignite.apache.org/viewModification.html?modId=902842
>  - semyon danilov 
> https://ci.ignite.apache.org/viewModification.html?modId=902900
>  - mikhail petrov <32207922+ololo3...@users.noreply.github.com>
> https://ci.ignite.apache.org/viewModification.html?modId=902915
>
>  - Here's a reminder of what contributors were agreed to do
> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
>  - Should you have any questions please contact
> dev@ignite.apache.org
>
> Best Regards,
> Apache Ignite TeamCity Bot
> https://github.com/apache/ignite-teamcity-bot
> Notification generated at 23:01:31 10-06-2020
>

Re: [DISCUSS] Fix confusing "Used by" on GitHub

[Ivan Pavlukhin]

Denis,

> However, you can always change it manually.

I spent a little time trying to find how but did not. Not sure that
today I can check it with INFRA timely. Actually I asked GitHub
support for help, see a conversation below.

2020-06-07 0:42 GMT+03:00, GitHub Developer Support
:
> ## Please do not write below this line ##
>
> Your request has been updated.
>
> You can add a comment by replying to this email.
>
> --
>
> Jamie Cansdale, Jun 6, 2020, 9:42:20 PM UTC
>
> Hello,
>
>> It displays usages for a one of Apache Ignite packages
>> (https://github.com/apache/ignite). And that package is not the most
>> used.
>
> I think it's pointing at this one because you're pointing at
> https://github.com/apache/ignite here:
> https://github.com/apache/ignite/blob/9d2824dd81e14c01a4e325e2ffe28f2608e2826e/modules/platforms/nodejs/package.json#L13
>
> ...but you aren't pointing pack to https://github.com/apache/ignite here:
> https://github.com/apache/ignite/blob/master/modules/core/pom.xml
>
> I think you might need a section like this:
> https://github.com/apache/ignite/blob/master/pom.xml#L38
>
> ...except pointing to https://github.com/apache/ignite
>
> This way GitHub can validate ownership of your package when it sees it
> published. Without this check, any repository could claim a package they
> didn't publish!
>
> I hope that helps!
>
> Regards,
> Jamie.
>
> --
>
> pavlukhin, Jun 2, 2020, 1:26:53 PM UTC
>
> Hi!
>
> How to configure "Used by" button on GitHub? It displays usages for a one of
> Apache Ignite packages (https://github.com/apache/ignite). And that package
> is not the most used. Is it possible to choose another package for counting
> usages or might be disable "Used by" button at all?
>
> Attachment(s):
> ignite-used-by.png -
> https://enterprise.githubsupport.com/attachments/token/AwAm2jptEyZQ9PRQQDXhrhVOI/?name=ignite-used-by.png
>
> 

2020-06-11 2:43 GMT+03:00, Denis Magda :
> I can see the badge being signed in.
>
> In fact, there are many more dependents on our modules and packages:
> https://github.com/apache/ignite/network/dependents
>
> The badge displays
> "apache-ignite-client" stats by default because the package goes first in
> the list. However, you can always change it manually. For instance, there
> are more than 1,400 dependants on ignite-core module:
> https://github.com/apache/ignite/network/dependents?package_id=UGFja2FnZS0xODE0MjIyNzE%3D
>
> Probably, it's possible to show the stats of ignite-core in the badge but I
> don't have access to the repo settings. Ivan, would you mind checking this
> with INFRA?
>
> -
> Denis
>
>
> On Wed, Jun 10, 2020 at 1:40 PM Ivan Pavlukhin  wrote:
>
>> A screenshot from my browser [1]. I suppose we still think about
>> proper repository URLs.
>>
>> P.S. I do not see "Used by" when I am not logged in. Might it be the
>> case?
>>
>> [1]
>> https://gist.githubusercontent.com/pavlukhin/c8c7c6266eeab56048c31f5cdfb31d20/raw/3858c12d7b65e3162297b704ba861e4945ed9ca4/ignite-used-by.png
>>
>> 2020-06-10 23:05 GMT+03:00, Ilya Kasnacheev :
>> > Hello!
>> >
>> > Still nothng. Maybe they are A/B testing this feature? In this case, I
>> > suggest we wait.
>> >
>> > Regards,
>> > --
>> > Ilya Kasnacheev
>> >
>> >
>> > ср, 10 июн. 2020 г. в 22:40, Pavel Tupitsyn :
>> >
>> >> Ilya, Andrey, try a forced reload of the page:
>> >> [image: image.png]
>> >>
>> >>
>> >> On Wed, Jun 10, 2020 at 10:30 PM Andrey Gura  wrote:
>> >>
>> >>> +1
>> >>>
>> >>> I don't see any badges.
>> >>>
>> >>> On Wed, Jun 10, 2020 at 10:27 PM Ilya Kasnacheev
>> >>>  wrote:
>> >>> >
>> >>> > Hello!
>> >>> >
>> >>> > I don't see such a badge. Instead I see "Watch" "Star" "Fork".
>> >>> >
>> >>> > Regards,
>> >>> > --
>> >>> > Ilya Kasnacheev
>> >>> >
>> >>> >
>> >>> > ср, 10 июн. 2020 г. в 20:58, Ivan Pavlukhin :
>> >>> >
>> >>> > > Hi Igniters,
>> >>> > >
>> >>> > > I noticed that we have a confusing "Used by" badge on a GitHub
>> >>> > > mirror
>> >>> > > repository main page [1] (the badge is located in a line with
>> >>> > > Star
>> >>> > > and
>> >>> > > Fork badges). It reports only a couple of usages while there are
>> >>> > > much
>> >>> > > more. Actually it shows only apache-ignite-client NPM package
>> >>> > > usages.
>> >>> > > As I understood it happens because only an NPM package config
>> >>> > > file
>> >>> > > refers a GitHub repository URL while e.g. maven modules refer to
>> >>> > > an
>> >>> > > ASF repository (GitBox) (see an  section in parent/pom.xml).
>> >>> > >
>> >>> > > IMHO a confusing usages number is a problem and it worth
>> >>> > > resolving.
>> >>> > > I
>> >>> > > see following options:
>> >>> > > 1. Use an ASF repository URL in the NPM package config file.
>> >>> > > 2. Use the GitHub repository URL for maven packages.
>> >>> > >
>> >>> > > While with the first option we will see no 

Re: Moving binary metadata to PDS storage folder

[Данилов Семён]

Hello everyone,

can we move forward with the merge of IGNITE-12994?

Semyon

18.05.2020, 19:08, "Denis Mekhanikov" :
> Users shouldn't care about binary_meta and marshaller directories. Those
> are internal details. Having to go through the documentation on those
> things to figure out whether you need to run each of the provided scripts
> or not will lead to terrible user experience.
> If we add the binary_marshaller_move.sh script for this specific case, it
> will stay with us forever just because migration from Ignite 2.8 to 2.9
> required running this thing.
>
> Denis

Re: Can I get write permissions for Apache Wiki?

[Данилов Семён]

Hello!

It's sdanilov

Regards,
Semyon Danilov

09.06.2020, 13:04, "Ilya Kasnacheev" :
> Hello!
>
> What is your login for apache wiki?
>
> Regards,
> --
> Ilya Kasnacheev
>
> вт, 9 июн. 2020 г. в 10:11, Данилов Семён :
>
>>  ello Igniters,
>>
>>  I’m planning to change
>>  
>> https://cwiki.apache.org/confluence/display/IGNITE/Ignite+Persistent+Store+-+under+the+hood
>>  (because I have pending pull request for changing binary meta location),
>>  but don’t have rights for this.
>>  Can someone please give me the access?
>>
>>  Sincerely yours,
>>  Semyon Danilov.