Re: gremlin cosine similarity
There really isn't anything pre-built into Gremlin for that. Daniel Kuppitz however did do some Gremlin magic with that at one point though: https://groups.google.com/g/gremlin-users/c/A7v-7bLoXeo/m/k2qaMylyHZcJ and for jaccard similarity: https://stackoverflow.com/a/55287231/1831717 On Wed, Jul 14, 2021 at 9:23 AM mehmet ikbal özmen wrote: > Hello > I'm trying to develop recommendation algorithm using gremlin. I'am looking > for cosine similarity built in function on the Internet. However I couldnt > find any resource for this issue. Could you share any documentation for > similarity algorithms implemented in Gremlin. > Best Regards > Mehmet > > -- > Mehmet İkbal Özmen > İstanbul Teknik Üniversitesi > Elektronik ve Haberleşme Mühendisliği >
Re: [DISCUSS] go driver
I would agree with considering Go as the next official GLV. In my conversations with Gremlin users, Go is by far the language I get asked about the most in terms of languages that we currently do not have a GLV for. Cheers,Kelvin On Thursday, July 15, 2021, 09:37:44 AM CDT, Joshua Shinavier wrote: +1 to official support for Go. In terms of popularity, it seems most often to land in the top 10 than the top 5 in developer lists, but anecdotally, it is increasingly used in companies that take after Google. My company has two officially supported languages, FWIW: Go (#1) and Java (#2). Josh On Wed, Jul 14, 2021 at 1:05 PM Stephen Mallette wrote: > If there were a candidate for another official Gremlin driver, I'd say that > it would have to be Go. I've heard more requests for official support there > than anything else. As far as I know there are no less than five different > third-party Go drivers out there right now which further leads me to > believe that folks want this functionality. > > I do have concerns about the additional overhead of yet another programming > language to support, but if it helps unify a programming language space > where we have a large number of users who would benefit, it's probably > worth considering. > > Happy to hear from anyone with thoughts about adding support for Go, > experience with any of the third-party Go drivers out there, etc. >
Re: [DISCUSS] gremlint 3.5.1 release candidate
Very cool! I gave it a quick test and it works! tor. 15. jul. 2021 kl. 16:45 skrev Stephen Mallette : > wow - first try: > > https://www.npmjs.com/package/gremlint > > > > > On Mon, Jul 12, 2021 at 2:28 PM Øyvind Sæbø wrote: > > > > > I don’t have a strong opinion on this, so if this is consistent with how > > it’s been done earlier it sounds good to me. Really excited to see we’re > > getting close to releasing Gremlint as a library:) > > > > Øyvind > > > > > 12. jul. 2021 kl. 18:09 skrev Stephen Mallette : > > > > > > As we'd discussed elsewhere, 3.5.1 should be good to release gremlint > as > > a > > > library. To ensure that it's all rigged up properly to deploy to npm on > > > release day, i think it's worth trying to publish a release candidate > > with > > > a beta tag as we first did with gremlin-javascript for 3.4.0-rc1. > > > > > > I realize "-rc1" isn't exactly the way javascript numbers these sorts > of > > > things, but perhaps we should try to just stay consistent with what > we've > > > always done. My understanding is that the actual version number we use > > has > > > less to do with a "beta" or "alpha" version than the usage of the --tag > > > value as in: > > > > > > npm publish --tag beta > > > > > > Assuming there are no concerns I'll go ahead with this initial try for > > > 3.5.1-rc1 in the next day or so. Thanks! > > >
AW: [DISCUSS] code freeze 3.4.12/3.5.1
Thanks for the heads up and good to know that the deployment worked for gremlint without any new issues coming up. I will probably republish the changed docs tomorrow and then continue with the release process at the start of next week. -Ursprüngliche Nachricht- Von: Stephen Mallette Gesendet: Donnerstag, 15. Juli 2021 16:50 An: dev@tinkerpop.apache.org Betreff: Re: [DISCUSS] code freeze 3.4.12/3.5.1 Florian, you probably noticed the other thread where the gremlint release candidate worked just fine. I updated the release docs on 3.5-dev to include the step to also release gremlint for 3.5.1. It is basically the same command as the one for gremlin-javascript so easy stuff. While you're free to follow the dev docs in /current for the release, note that there is this little addition to that process that won't be present in .current as you're going through the steps. On Thu, Jul 15, 2021 at 9:57 AM Stephen Mallette wrote: > I just pushed a change for upgrade docs on 3.5.1. If you feel like > republishing toward the end of code freeze you can, but it's not > necessary in this case i don't think. Note that you can selectively > update documentation, but the task is a bit of a manual one: > > 1. bin/process-docs.sh --dryRun > 2. in target/postprocess-asciidoc manually delete the folder(s) you > want to regenerate content for 3. bin/process-docs.sh (this will only > generate docs for the stuff you > deleted) > 4. you can then do an: svn checkout > https://svn.apache.org/repos/asf/tinkerpop/site/docs// containing the file you want to update> 5. copy the newly generated > file in target/docs over the old one in the svn directory 6. svn > commit your change > > In this case, it's even easier because you probably just care about > upgrade docs really. since upgrade docs are static you can skip steps > 2 and > 3 as the doc should already be in good order as there are no code > examples to pass through the script engine. > > > > > On Wed, Jul 14, 2021 at 6:51 AM Florian Hockmann > > wrote: > >> I’ve published SNAPSHOT artifacts and docs for review: >> >> https://tinkerpop.apache.org/docs/3.4.12-SNAPSHOT/ >> https://tinkerpop.apache.org/docs/3.5.1-SNAPSHOT/ >> >> -Ursprüngliche Nachricht- >> Von: Stephen Mallette >> Gesendet: Freitag, 9. Juli 2021 16:23 >> An: dev@tinkerpop.apache.org >> Betreff: Re: [DISCUSS] code freeze 3.4.12/3.5.1 >> >> > Stephen already mentioned in the discussion thread on 3.5.1 that >> > he >> intends to merge a PR in for 3.5.1 around gremlin-language that he >> considers to be low risk. >> >> i think i will pull back on that. it's turning into more work than >> i'd expected. no need to expect further code changes from me. >> >> On Fri, Jul 9, 2021 at 4:01 AM Florian Hockmann >> >> wrote: >> >> > Code freeze on 3.4-dev and 3.5-dev starts now. I don't see any open >> > issues in JIRA that are tagged for this release or open PRs that >> > need to be merged. >> > If you have anything that should be included in these releases, >> > then please respond to this thread. Stephen already mentioned in >> > the discussion thread on 3.5.1 that he intends to merge a PR in for >> > 3.5.1 around gremlin-language that he considers to be low risk. >> > >> > >> > >> > I will be publishing SNAPSHOT artifacts and documentation for >> > testing/review and will post back here when that is available. >> > >> > >> > >> > Please use this thread for any issues that come up during the code >> > freeze time frame. Thanks. >> > >> > >> >>
Re: [DISCUSS] code freeze 3.4.12/3.5.1
Florian, you probably noticed the other thread where the gremlint release candidate worked just fine. I updated the release docs on 3.5-dev to include the step to also release gremlint for 3.5.1. It is basically the same command as the one for gremlin-javascript so easy stuff. While you're free to follow the dev docs in /current for the release, note that there is this little addition to that process that won't be present in .current as you're going through the steps. On Thu, Jul 15, 2021 at 9:57 AM Stephen Mallette wrote: > I just pushed a change for upgrade docs on 3.5.1. If you feel like > republishing toward the end of code freeze you can, but it's not necessary > in this case i don't think. Note that you can selectively update > documentation, but the task is a bit of a manual one: > > 1. bin/process-docs.sh --dryRun > 2. in target/postprocess-asciidoc manually delete the folder(s) you want > to regenerate content for > 3. bin/process-docs.sh (this will only generate docs for the stuff you > deleted) > 4. you can then do an: svn checkout > https://svn.apache.org/repos/asf/tinkerpop/site/docs// containing the file you want to update> > 5. copy the newly generated file in target/docs over the old one in the > svn directory > 6. svn commit your change > > In this case, it's even easier because you probably just care about > upgrade docs really. since upgrade docs are static you can skip steps 2 and > 3 as the doc should already be in good order as there are no code examples > to pass through the script engine. > > > > > On Wed, Jul 14, 2021 at 6:51 AM Florian Hockmann > wrote: > >> I’ve published SNAPSHOT artifacts and docs for review: >> >> https://tinkerpop.apache.org/docs/3.4.12-SNAPSHOT/ >> https://tinkerpop.apache.org/docs/3.5.1-SNAPSHOT/ >> >> -Ursprüngliche Nachricht- >> Von: Stephen Mallette >> Gesendet: Freitag, 9. Juli 2021 16:23 >> An: dev@tinkerpop.apache.org >> Betreff: Re: [DISCUSS] code freeze 3.4.12/3.5.1 >> >> > Stephen already mentioned in the discussion thread on 3.5.1 that he >> intends to merge a PR in for 3.5.1 around gremlin-language that he >> considers to be low risk. >> >> i think i will pull back on that. it's turning into more work than i'd >> expected. no need to expect further code changes from me. >> >> On Fri, Jul 9, 2021 at 4:01 AM Florian Hockmann >> wrote: >> >> > Code freeze on 3.4-dev and 3.5-dev starts now. I don't see any open >> > issues in JIRA that are tagged for this release or open PRs that need >> > to be merged. >> > If you have anything that should be included in these releases, then >> > please respond to this thread. Stephen already mentioned in the >> > discussion thread on 3.5.1 that he intends to merge a PR in for 3.5.1 >> > around gremlin-language that he considers to be low risk. >> > >> > >> > >> > I will be publishing SNAPSHOT artifacts and documentation for >> > testing/review and will post back here when that is available. >> > >> > >> > >> > Please use this thread for any issues that come up during the code >> > freeze time frame. Thanks. >> > >> > >> >>
Re: [DISCUSS] gremlint 3.5.1 release candidate
wow - first try: https://www.npmjs.com/package/gremlint On Mon, Jul 12, 2021 at 2:28 PM Øyvind Sæbø wrote: > > I don’t have a strong opinion on this, so if this is consistent with how > it’s been done earlier it sounds good to me. Really excited to see we’re > getting close to releasing Gremlint as a library:) > > Øyvind > > > 12. jul. 2021 kl. 18:09 skrev Stephen Mallette : > > > > As we'd discussed elsewhere, 3.5.1 should be good to release gremlint as > a > > library. To ensure that it's all rigged up properly to deploy to npm on > > release day, i think it's worth trying to publish a release candidate > with > > a beta tag as we first did with gremlin-javascript for 3.4.0-rc1. > > > > I realize "-rc1" isn't exactly the way javascript numbers these sorts of > > things, but perhaps we should try to just stay consistent with what we've > > always done. My understanding is that the actual version number we use > has > > less to do with a "beta" or "alpha" version than the usage of the --tag > > value as in: > > > > npm publish --tag beta > > > > Assuming there are no concerns I'll go ahead with this initial try for > > 3.5.1-rc1 in the next day or so. Thanks! >
Re: [DISCUSS] go driver
+1 to official support for Go. In terms of popularity, it seems most often to land in the top 10 than the top 5 in developer lists, but anecdotally, it is increasingly used in companies that take after Google. My company has two officially supported languages, FWIW: Go (#1) and Java (#2). Josh On Wed, Jul 14, 2021 at 1:05 PM Stephen Mallette wrote: > If there were a candidate for another official Gremlin driver, I'd say that > it would have to be Go. I've heard more requests for official support there > than anything else. As far as I know there are no less than five different > third-party Go drivers out there right now which further leads me to > believe that folks want this functionality. > > I do have concerns about the additional overhead of yet another programming > language to support, but if it helps unify a programming language space > where we have a large number of users who would benefit, it's probably > worth considering. > > Happy to hear from anyone with thoughts about adding support for Go, > experience with any of the third-party Go drivers out there, etc. >
Re: [DISCUSS] code freeze 3.4.12/3.5.1
I just pushed a change for upgrade docs on 3.5.1. If you feel like republishing toward the end of code freeze you can, but it's not necessary in this case i don't think. Note that you can selectively update documentation, but the task is a bit of a manual one: 1. bin/process-docs.sh --dryRun 2. in target/postprocess-asciidoc manually delete the folder(s) you want to regenerate content for 3. bin/process-docs.sh (this will only generate docs for the stuff you deleted) 4. you can then do an: svn checkout https://svn.apache.org/repos/asf/tinkerpop/site/docs// 5. copy the newly generated file in target/docs over the old one in the svn directory 6. svn commit your change In this case, it's even easier because you probably just care about upgrade docs really. since upgrade docs are static you can skip steps 2 and 3 as the doc should already be in good order as there are no code examples to pass through the script engine. On Wed, Jul 14, 2021 at 6:51 AM Florian Hockmann wrote: > I’ve published SNAPSHOT artifacts and docs for review: > > https://tinkerpop.apache.org/docs/3.4.12-SNAPSHOT/ > https://tinkerpop.apache.org/docs/3.5.1-SNAPSHOT/ > > -Ursprüngliche Nachricht- > Von: Stephen Mallette > Gesendet: Freitag, 9. Juli 2021 16:23 > An: dev@tinkerpop.apache.org > Betreff: Re: [DISCUSS] code freeze 3.4.12/3.5.1 > > > Stephen already mentioned in the discussion thread on 3.5.1 that he > intends to merge a PR in for 3.5.1 around gremlin-language that he > considers to be low risk. > > i think i will pull back on that. it's turning into more work than i'd > expected. no need to expect further code changes from me. > > On Fri, Jul 9, 2021 at 4:01 AM Florian Hockmann > wrote: > > > Code freeze on 3.4-dev and 3.5-dev starts now. I don't see any open > > issues in JIRA that are tagged for this release or open PRs that need > > to be merged. > > If you have anything that should be included in these releases, then > > please respond to this thread. Stephen already mentioned in the > > discussion thread on 3.5.1 that he intends to merge a PR in for 3.5.1 > > around gremlin-language that he considers to be low risk. > > > > > > > > I will be publishing SNAPSHOT artifacts and documentation for > > testing/review and will post back here when that is available. > > > > > > > > Please use this thread for any issues that come up during the code > > freeze time frame. Thanks. > > > > > >
