[
https://issues.apache.org/jira/browse/SOLR-14048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16995331#comment-16995331
]
ASF subversion and git services commented on SOLR-14048:
--------------------------------------------------------
Commit c021a253fea7c9922b72ed50c1eaf2aac1f53b72 in lucene-solr's branch
refs/heads/branch_8x from Kevin Risden
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=c021a25 ]
SOLR-14048: Improve Hadoop test sanity checks
Signed-off-by: Kevin Risden <kris...@apache.org>
> Improve Hadoop test sanity checks
> ---------------------------------
>
> Key: SOLR-14048
> URL: https://issues.apache.org/jira/browse/SOLR-14048
> Project: Solr
> Issue Type: Test
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Hadoop Integration, hdfs, Tests
> Reporter: Kevin Risden
> Assignee: Kevin Risden
> Priority: Major
> Fix For: 8.5
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Add more checks around the Hadoop modified classes we use.
> Some ideas from [~hossman] in SOLR-14033
> * some dev docs (package level javadocs?) explaining the whole
> {{org.apache.hadoop}} "shadow" class impls
> * ideally include some hook in {{HdfsTestUtil}} that causes it to fail fast
> if it can detect that the classloader didn't pick up our modified classes? ..
> maybe by adding a new {{public static final Object
> SOLR_HACK_FOR_CLASS_VERIFICATION = new Object}} to each
> {{org.apache.hadoop.\*\*}} that it could check for via reflection?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
