markrmiller commented on pull request #300:
URL: https://github.com/apache/solr/pull/300#issuecomment-958959533
Won't do. Will avoid ideal solution for these rarer of cases, will do waits
/ hacks / alternatives in line with current approaches in individual issues as
necessary.
--
This i
markrmiller commented on pull request #300:
URL: https://github.com/apache/solr/pull/300#issuecomment-958959533
--
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 unsubscri
markrmiller commented on pull request #300:
URL: https://github.com/apache/solr/pull/300#issuecomment-958959533
Won't do. Will avoid ideal solution for these rarer of cases, will do waits
/ hacks / alternatives in line with current approaches in individual issues as
necessary.
--
This i
markrmiller commented on pull request #300:
URL: https://github.com/apache/solr/pull/300#issuecomment-948387105
No I'm not, I dont think mike understands what this pr is about.
I say what I'm doing above in the comment right above yours.
--
This is an automated message from the Apa
markrmiller commented on pull request #300:
URL: https://github.com/apache/solr/pull/300#issuecomment-938669235
It turns out I may end up ditching this PR. The primary test it would be
used for is an HDFS test, and then also the rest of the HDFS tests (which can
be dealt with alternatively
markrmiller commented on pull request #300:
URL: https://github.com/apache/solr/pull/300#issuecomment-935292836
I only just learned of the draft option. This is ripped from other code, I
will update it after it's modified for use in an issue.
--
This is an automated message from the Apac
