[GitHub] [lucene-jira-archive] mocobeta closed issue #127: Consider using GitHub Pages for attachments rather than raw.githubusercontent.com

mocobeta closed issue #127: Consider using GitHub Pages for attachments rather than raw.githubusercontent.com URL: https://github.com/apache/lucene-jira-archive/issues/127 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use t

[GitHub] [lucene-jira-archive] mocobeta opened a new issue, #144: Links to Jira issue comments are not converted to GitHub issue comments

mocobeta opened a new issue, #144: URL: https://github.com/apache/lucene-jira-archive/issues/144 We convert Jira cross-issue links (LUCENE-) to GitHub issue links (#NN). However, links to Jira comments are not converted into GitHub comments since we don't have a mapping from Jira comm

[GitHub] [lucene] rmuir commented on pull request #1057: LUCENE-10670: Add a codec class to track merge time of each index part

rmuir commented on PR #1057: URL: https://github.com/apache/lucene/pull/1057#issuecomment-1212962044 dude, that's nothing compared to the cost of disabling bulk merge, which will also force all stored fields to be recompressed every merge as well. sorry, i'm completely against this PR

[GitHub] [lucene-jira-archive] mikemccand opened a new pull request, #145: Polish INFRA instructions a bit

mikemccand opened a new pull request, #145: URL: https://github.com/apache/lucene-jira-archive/pull/145 I made a few possible polish edits for the INFRA instructions, plus one question. -- This is an automated message from the Apache Git Service. To respond to the message, please log on t

[GitHub] [lucene-jira-archive] mikemccand commented on a diff in pull request #145: Polish INFRA instructions a bit

mikemccand commented on code in PR #145: URL: https://github.com/apache/lucene-jira-archive/pull/145#discussion_r944368903 ## migration/instructions-for-infra-team.md: ## @@ -77,17 +77,19 @@ JiraKey,GitHubUrl,GitHubNumber LUCENE-1,https://github.com/apache/lucene/issues/1080,1

[GitHub] [lucene-jira-archive] mocobeta commented on a diff in pull request #145: Polish INFRA instructions a bit

mocobeta commented on code in PR #145: URL: https://github.com/apache/lucene-jira-archive/pull/145#discussion_r944385229 ## migration/instructions-for-infra-team.md: ## @@ -77,17 +77,19 @@ JiraKey,GitHubUrl,GitHubNumber LUCENE-1,https://github.com/apache/lucene/issues/1080,108

[GitHub] [lucene-jira-archive] mikemccand commented on a diff in pull request #145: Polish INFRA instructions a bit

mikemccand commented on code in PR #145: URL: https://github.com/apache/lucene-jira-archive/pull/145#discussion_r944386278 ## migration/instructions-for-infra-team.md: ## @@ -77,17 +77,19 @@ JiraKey,GitHubUrl,GitHubNumber LUCENE-1,https://github.com/apache/lucene/issues/1080,1

[GitHub] [lucene-jira-archive] mocobeta commented on a diff in pull request #145: Polish INFRA instructions a bit

mocobeta commented on code in PR #145: URL: https://github.com/apache/lucene-jira-archive/pull/145#discussion_r944395455 ## migration/instructions-for-infra-team.md: ## @@ -35,7 +35,7 @@ GH-LUCENE-10677.json # set the GitHub PAT token to an env variable migration $ cp .env.ex

[GitHub] [lucene-jira-archive] mocobeta commented on a diff in pull request #145: Polish INFRA instructions a bit

mocobeta commented on code in PR #145: URL: https://github.com/apache/lucene-jira-archive/pull/145#discussion_r944395455 ## migration/instructions-for-infra-team.md: ## @@ -35,7 +35,7 @@ GH-LUCENE-10677.json # set the GitHub PAT token to an env variable migration $ cp .env.ex

[GitHub] [lucene-jira-archive] mocobeta commented on a diff in pull request #145: Polish INFRA instructions a bit

mocobeta commented on code in PR #145: URL: https://github.com/apache/lucene-jira-archive/pull/145#discussion_r944395455 ## migration/instructions-for-infra-team.md: ## @@ -35,7 +35,7 @@ GH-LUCENE-10677.json # set the GitHub PAT token to an env variable migration $ cp .env.ex

[GitHub] [lucene-jira-archive] mocobeta commented on a diff in pull request #145: Polish INFRA instructions a bit

mocobeta commented on code in PR #145: URL: https://github.com/apache/lucene-jira-archive/pull/145#discussion_r944408114 ## migration/instructions-for-infra-team.md: ## @@ -77,17 +77,19 @@ JiraKey,GitHubUrl,GitHubNumber LUCENE-1,https://github.com/apache/lucene/issues/1080,108

[GitHub] [lucene-jira-archive] mikemccand merged pull request #145: Polish INFRA instructions a bit

mikemccand merged PR #145: URL: https://github.com/apache/lucene-jira-archive/pull/145 -- 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..

[GitHub] [lucene] msokolov commented on pull request #1057: LUCENE-10670: Add a codec class to track merge time of each index part

msokolov commented on PR #1057: URL: https://github.com/apache/lucene/pull/1057#issuecomment-1213141620 Thanks for helping out here, @rmuir - can you explain how it is that bulk operations would be prevented by this change? I don't really understand, but maybe if you explained we could figu

[GitHub] [lucene-jira-archive] mocobeta commented on issue #104: Should we regenerate another full export?

mocobeta commented on issue #104: URL: https://github.com/apache/lucene-jira-archive/issues/104#issuecomment-1213212384 I checked several issues from new to old. I see no degradations from the previous one. If you are okay with that, the actual migration will be the same as this exc

[GitHub] [lucene-jira-archive] mikemccand closed issue #104: Should we regenerate another full export?

mikemccand closed issue #104: Should we regenerate another full export? URL: https://github.com/apache/lucene-jira-archive/issues/104 -- 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 comm

[GitHub] [lucene-jira-archive] mikemccand commented on issue #104: Should we regenerate another full export?

mikemccand commented on issue #104: URL: https://github.com/apache/lucene-jira-archive/issues/104#issuecomment-1213220222 +1, let's close this, yay!! Thank you @mocobeta! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and u

[GitHub] [lucene-jira-archive] mocobeta commented on issue #104: Should we regenerate another full export?

mocobeta commented on issue #104: URL: https://github.com/apache/lucene-jira-archive/issues/104#issuecomment-1213225632 Thank you, please open reports if you notice anything. I think we still have some time for small improvements. -- This is an automated message from the Apache Git Servi

[GitHub] [lucene-jira-archive] mocobeta commented on issue #93: Too much text is quoted

mocobeta commented on issue #93: URL: https://github.com/apache/lucene-jira-archive/issues/93#issuecomment-1213246144 Incorrect quotes are misleading. I'd like to manage to address this... I think it is difficult to correctly insert line feeds like this. > EG running merges (or

[GitHub] [lucene] nknize merged pull request #1066: LUCENE-10654: Fix Shape Bounding Box Inconsistencies

nknize merged PR #1066: URL: https://github.com/apache/lucene/pull/1066 -- 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.apache

[jira] [Commented] (LUCENE-10654) New companion doc value format for LatLonShape and XYShape field types

[ https://issues.apache.org/jira/browse/LUCENE-10654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17579030#comment-17579030 ] ASF subversion and git services commented on LUCENE-10654: -- Co

[GitHub] [lucene] nknize opened a new pull request, #1067: LUCENE-10654: Fix ShapeDocValue Bounding Box failure (#1066)

nknize opened a new pull request, #1067: URL: https://github.com/apache/lucene/pull/1067 Backport of #1066 to 9x The base spatial test case may create invalid self crossing polygons. These polygons are cleaned by the tessellator which may result in an inconsistent bounding box be

[GitHub] [lucene] nknize merged pull request #1067: LUCENE-10654: Fix ShapeDocValue Bounding Box failure (#1066)

nknize merged PR #1067: URL: https://github.com/apache/lucene/pull/1067 -- 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.apache

[jira] [Commented] (LUCENE-10654) New companion doc value format for LatLonShape and XYShape field types

[ https://issues.apache.org/jira/browse/LUCENE-10654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17579057#comment-17579057 ] ASF subversion and git services commented on LUCENE-10654: -- Co

[GitHub] [lucene-jira-archive] mocobeta opened a new pull request, #146: Escape '>' to avoid wrong quotes in markdown

mocobeta opened a new pull request, #146: URL: https://github.com/apache/lucene-jira-archive/pull/146 #93 `>` should be escaped 1) if it appears at the end of the line, and also 2) is not a part of any expression grammar. It's possible to do such selective escape by tweaking the syn

[GitHub] [lucene-jira-archive] mocobeta commented on issue #93: Too much text is quoted

mocobeta commented on issue #93: URL: https://github.com/apache/lucene-jira-archive/issues/93#issuecomment-1213650299 I opened workaround PR #146. -- 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