accumulo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ivakegg <>
Subject [GitHub] accumulo pull request #260: ACCUMULO-4643 initial implementation
Date Sat, 03 Jun 2017 18:47:11 GMT
Github user ivakegg commented on a diff in the pull request:
    --- Diff: iterator-test-harness/src/main/java/org/apache/accumulo/iteratortest/testcases/
    @@ -0,0 +1,77 @@
    + * Licensed to the Apache Software Foundation (ASF) under one or more
    + * contributor license agreements.  See the NOTICE file distributed with
    + * this work for additional information regarding copyright ownership.
    + * The ASF licenses this file to you under the Apache License, Version 2.0
    + * (the "License"); you may not use this file except in compliance with
    + * the License.  You may obtain a copy of the License at
    + *
    + *
    + *
    + * Unless required by applicable law or agreed to in writing, software
    + * distributed under the License is distributed on an "AS IS" BASIS,
    + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    + * See the License for the specific language governing permissions and
    + * limitations under the License.
    + */
    +package org.apache.accumulo.iteratortest.testcases;
    +import org.apache.accumulo.core.iterators.SortedKeyValueIterator;
    +import org.apache.accumulo.core.iterators.YieldCallback;
    +import org.apache.accumulo.iteratortest.IteratorTestInput;
    +import org.apache.accumulo.iteratortest.IteratorTestOutput;
    +import org.apache.accumulo.iteratortest.IteratorTestUtil;
    +import org.apache.accumulo.iteratortest.environments.SimpleIteratorEnvironment;
    +import java.util.TreeMap;
    + * Test case that verifies that an iterator works correctly with the yielding api. Note
that most iterators do nothing in terms of yielding in which case this
    + * merely tests that the iterator produces the correct output. If however the iterator
does override the yielding api, then this ensures that it works correctly
    + * iff the iterator actually decides to yield. Nothing can force an iterator to yield
without knowing something about the internals of the iterator being
    + * tested.
    + */
    +public class YieldingTestCase extends OutputVerifyingTestCase {
    --- End diff --
    I thought that this structure was a reasonable mechanism to ensure that the basic expectations
of an iterator are met.  In this case, I am not positive it adds much because this test case
by itself cannot force the implemented iterator to yield.  However if the implementer could
provide a mechanism to force his/her iterator to yield, then this might prove useful.

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message