[GitHub] [lucene-jira-archive] mocobeta commented on issue #4: Which GitHub accont we should/can use for migration?

2022-07-02 Thread GitBox
mocobeta commented on issue #4: URL: https://github.com/apache/lucene-jira-archive/issues/4#issuecomment-1173024383 If there are no comments/objections, I'll decide how we proceed with that. -- This is an automated message from the Apache Git Service. To respond to the message, please log

[GitHub] [lucene-jira-archive] mocobeta commented on issue #4: Which GitHub accont we should/can use for migration?

2022-07-02 Thread GitBox
mocobeta commented on issue #4: URL: https://github.com/apache/lucene-jira-archive/issues/4#issuecomment-1173022411 If we must use an ASF bot account throughout all processes, I'd break up the second pass into three sub-steps. 1) dump all issues/comments again from GitHub 2) convert

[GitHub] [lucene-jira-archive] mocobeta commented on issue #4: Which GitHub accont we should/can use for migration?

2022-07-02 Thread GitBox
mocobeta commented on issue #4: URL: https://github.com/apache/lucene-jira-archive/issues/4#issuecomment-1173020248 This is two-pass migration. 1. First pass: import all issues/comments; this has to be done by an infra account. I think we can ask infra to use an official ASF b

[GitHub] [lucene-jira-archive] mocobeta closed issue #13: Test issue

2022-07-02 Thread GitBox
mocobeta closed issue #13: Test issue URL: https://github.com/apache/lucene-jira-archive/issues/13 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issue

[GitHub] [lucene-jira-archive] mocobeta opened a new issue, #14: Investigate import failure of LUCENE-1498

2022-07-02 Thread GitBox
mocobeta opened a new issue, #14: URL: https://github.com/apache/lucene-jira-archive/issues/14 https://issues.apache.org/jira/browse/LUCENE-1498 won't be imported. ``` [2022-06-26 18:38:25,394] ERROR:import_github_issues: Import GitHub issue /mnt/hdd/repo/sandbox-lucene-10557/migra

[GitHub] [lucene-jira-archive] mocobeta commented on issue #7: Make a detailed migration plan

2022-07-02 Thread GitBox
mocobeta commented on issue #7: URL: https://github.com/apache/lucene-jira-archive/issues/7#issuecomment-1173010491 #13 confirmed that my account was able to update issues in an ASF repo without modifying the author. We can do step 7 (second pass - the most time-consuming part) ourselves.

[GitHub] [lucene-jira-archive] mocobeta commented on issue #13: Test issue

2022-07-02 Thread GitBox
mocobeta commented on issue #13: URL: https://github.com/apache/lucene-jira-archive/issues/13#issuecomment-1173010229 Ok, we can update issues ourselves by scripts. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the

[GitHub] [lucene-jira-archive] mocobeta commented on issue #13: Test issue

2022-07-02 Thread GitBox
mocobeta commented on issue #13: URL: https://github.com/apache/lucene-jira-archive/issues/13#issuecomment-1173007101 Thanks! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific commen

[GitHub] [lucene-jira-archive] ikawaha commented on issue #13: Test issue

2022-07-02 Thread GitBox
ikawaha commented on issue #13: URL: https://github.com/apache/lucene-jira-archive/issues/13#issuecomment-1173006810 ねこですねこはいますよろしくおねがいします -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the spe

[GitHub] [lucene-jira-archive] mocobeta commented on issue #13: Test issue

2022-07-02 Thread GitBox
mocobeta commented on issue #13: URL: https://github.com/apache/lucene-jira-archive/issues/13#issuecomment-1173006761 Thank you @ikawaha. Can you please also add a fake comment please? -- This is an automated message from the Apache Git Service. To respond to the message, please log on

[GitHub] [lucene-jira-archive] ikawaha opened a new issue, #13: Test issue

2022-07-02 Thread GitBox
ikawaha opened a new issue, #13: URL: https://github.com/apache/lucene-jira-archive/issues/13 This is a test to check the operation of the issue. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to t

[jira] [Commented] (LUCENE-10577) Quantize vector values

2022-07-02 Thread ASF subversion and git services (Jira)
[ https://issues.apache.org/jira/browse/LUCENE-10577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17561790#comment-17561790 ] ASF subversion and git services commented on LUCENE-10577: -- Co

[jira] [Commented] (LUCENE-10635) Ensure test coverage for WANDScorer after additional scorers get added

2022-07-02 Thread Zach Chen (Jira)
[ https://issues.apache.org/jira/browse/LUCENE-10635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17561789#comment-17561789 ] Zach Chen commented on LUCENE-10635: I like this idea! This approach should also be

[GitHub] [lucene] zacharymorn commented on pull request #972: LUCENE-10480: Use BMM scorer for 2 clauses disjunction

2022-07-02 Thread GitBox
zacharymorn commented on PR #972: URL: https://github.com/apache/lucene/pull/972#issuecomment-1172956347 Thanks again @jpountz ! I've created the above PR to backport these changes to `branch_9x`. -- This is an automated message from the Apache Git Service. To respond to the message, ple

[GitHub] [lucene] zacharymorn opened a new pull request, #1002: LUCENE-10480: (Backporting) Use BMM scorer for 2 clauses disjunction

2022-07-02 Thread GitBox
zacharymorn opened a new pull request, #1002: URL: https://github.com/apache/lucene/pull/1002 This PR backports PR https://github.com/apache/lucene/pull/972 to `branch_9x` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and us

[jira] [Commented] (LUCENE-10480) Specialize 2-clauses disjunctions

2022-07-02 Thread ASF subversion and git services (Jira)
[ https://issues.apache.org/jira/browse/LUCENE-10480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17561787#comment-17561787 ] ASF subversion and git services commented on LUCENE-10480: -- Co

[GitHub] [lucene] zacharymorn merged pull request #972: LUCENE-10480: Use BMM scorer for 2 clauses disjunction

2022-07-02 Thread GitBox
zacharymorn merged PR #972: URL: https://github.com/apache/lucene/pull/972 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@lucene.apa

[jira] [Commented] (LUCENE-10577) Quantize vector values

2022-07-02 Thread ASF subversion and git services (Jira)
[ https://issues.apache.org/jira/browse/LUCENE-10577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17561773#comment-17561773 ] ASF subversion and git services commented on LUCENE-10577: -- Co

[GitHub] [lucene] jtibshirani merged pull request #998: LUCENE-10577: Add vectors format unit test and fix toString

2022-07-02 Thread GitBox
jtibshirani merged PR #998: URL: https://github.com/apache/lucene/pull/998 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@lucene.apa

[GitHub] [lucene] jtibshirani commented on pull request #998: LUCENE-10577: Add vectors format unit test and fix toString

2022-07-02 Thread GitBox
jtibshirani commented on PR #998: URL: https://github.com/apache/lucene/pull/998#issuecomment-1172928401 No problem! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To uns

[GitHub] [lucene] jtibshirani commented on a diff in pull request #932: LUCENE-10559: Add Prefilter Option to KnnGraphTester

2022-07-02 Thread GitBox
jtibshirani commented on code in PR #932: URL: https://github.com/apache/lucene/pull/932#discussion_r912381221 ## lucene/core/src/test/org/apache/lucene/util/hnsw/KnnGraphTester.java: ## @@ -480,11 +537,15 @@ private int[][] getNN(Path docPath, Path queryPath) throws IOExceptio

[jira] [Commented] (LUCENE-10639) WANDScorer performs better without two-phase

2022-07-02 Thread Greg Miller (Jira)
[ https://issues.apache.org/jira/browse/LUCENE-10639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17561772#comment-17561772 ] Greg Miller commented on LUCENE-10639: -- {quote}I suspected there was some overhead

[jira] [Commented] (LUCENE-10635) Ensure test coverage for WANDScorer after additional scorers get added

2022-07-02 Thread Adrien Grand (Jira)
[ https://issues.apache.org/jira/browse/LUCENE-10635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17561754#comment-17561754 ] Adrien Grand commented on LUCENE-10635: --- Thinking out loud, maybe one way to do t

[jira] [Commented] (LUCENE-10639) WANDScorer performs better without two-phase

2022-07-02 Thread Adrien Grand (Jira)
[ https://issues.apache.org/jira/browse/LUCENE-10639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17561753#comment-17561753 ] Adrien Grand commented on LUCENE-10639: --- On a recent PR [~ChrisHegarty] found out

[jira] [Commented] (LUCENE-10639) WANDScorer performs better without two-phase

2022-07-02 Thread Adrien Grand (Jira)
[ https://issues.apache.org/jira/browse/LUCENE-10639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17561751#comment-17561751 ] Adrien Grand commented on LUCENE-10639: --- I suspected there was some overhead to t

[jira] [Created] (LUCENE-10639) WANDScorer performs better without two-phase

2022-07-02 Thread Greg Miller (Jira)
Greg Miller created LUCENE-10639: Summary: WANDScorer performs better without two-phase Key: LUCENE-10639 URL: https://issues.apache.org/jira/browse/LUCENE-10639 Project: Lucene - Core Issue

[GitHub] [lucene-jira-archive] mocobeta commented on issue #12: Make a test set for improving markup conversion quality

2022-07-02 Thread GitBox
mocobeta commented on issue #12: URL: https://github.com/apache/lucene-jira-archive/issues/12#issuecomment-1172897263 Supported block elements in [Jira Text Formatting](https://jira.atlassian.com/secure/WikiRendererHelpAction.jspa?section=all) - `-`: not included - `o`: correctly

[GitHub] [lucene] gsmiller commented on a diff in pull request #974: LUCENE-10614: Properly support getTopChildren in RangeFacetCounts

2022-07-02 Thread GitBox
gsmiller commented on code in PR #974: URL: https://github.com/apache/lucene/pull/974#discussion_r912362078 ## lucene/demo/src/java/org/apache/lucene/demo/facet/DistanceFacetsExample.java: ## @@ -212,7 +212,26 @@ public static Query getBoundingBoxQuery( } /** User runs a

[GitHub] [lucene-jira-archive] mocobeta commented on issue #2: Archive all Jira attachments

2022-07-02 Thread GitBox
mocobeta commented on issue #2: URL: https://github.com/apache/lucene-jira-archive/issues/2#issuecomment-1172890744 > This is first time I learned of this cool `dust` command! What a great name too. Yes, it's one of my favorite CLI tools (a bit slower than `du` but fine for my usage

[GitHub] [lucene-jira-archive] mikemccand commented on issue #2: Archive all Jira attachments

2022-07-02 Thread GitBox
mikemccand commented on issue #2: URL: https://github.com/apache/lucene-jira-archive/issues/2#issuecomment-1172888349 Thanks @mocobeta! This is first time I learned of this cool `dust` command! What a great name too. -- This is an automated message from the Apache Git Service. To respo

[GitHub] [lucene-jira-archive] mocobeta commented on issue #2: Archive all Jira attachments

2022-07-02 Thread GitBox
mocobeta commented on issue #2: URL: https://github.com/apache/lucene-jira-archive/issues/2#issuecomment-1172884299 Links that point to the files in the `attachments` branch are also fine. ![Screenshot from 2022-07-02 20-39-13](https://user-images.githubusercontent.com/1825333/176999

[GitHub] [lucene-jira-archive] mocobeta commented on issue #2: Archive all Jira attachments

2022-07-02 Thread GitBox
mocobeta commented on issue #2: URL: https://github.com/apache/lucene-jira-archive/issues/2#issuecomment-1172880262 Instead of `main`, I committed all attachments (the latest snapshot) to `attachments` branch. The download script looks to work fine. I'm closing this. -- This is an aut

[GitHub] [lucene-jira-archive] mocobeta closed issue #2: Archive all Jira attachments

2022-07-02 Thread GitBox
mocobeta closed issue #2: Archive all Jira attachments URL: https://github.com/apache/lucene-jira-archive/issues/2 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscrib

[GitHub] [lucene-jira-archive] mocobeta opened a new issue, #12: Make a test set for #1

2022-07-02 Thread GitBox
mocobeta opened a new issue, #12: URL: https://github.com/apache/lucene-jira-archive/issues/12 There are too many patterns where markup can be broken. Can't make sure that an ad-hoc fix for one problem does not introduce another bug. Instead of arbitrary choosing examples, it'd be good to

[GitHub] [lucene-jira-archive] mocobeta commented on issue #11: Selectively create github cross-issue link

2022-07-02 Thread GitBox
mocobeta commented on issue #11: URL: https://github.com/apache/lucene-jira-archive/issues/11#issuecomment-1172875774 It's awkward but may not be a blocker. At least we need to check if this does not break hyperlinks. -- This is an automated message from the Apache Git Service. To respon

[GitHub] [lucene-jira-archive] mocobeta opened a new issue, #11: Selectively create github cross-issue link

2022-07-02 Thread GitBox
mocobeta opened a new issue, #11: URL: https://github.com/apache/lucene-jira-archive/issues/11 Currently, we blindly create cross-issue links - for example, "LUCENE-.patch" is incorrectly replaced with "LUCENE- (#YYY).patch". Ideally, only Jira issue keys should be replaced. As a