Fix Javadocs, minor code tweaks

I suppose it would, for consistency. We can revisit the overall decision
later if needed, if it proves to again be a practical problem.

On Wed, Sep 17, 2014 at 8:35 PM, Suneel Marthi <notifications@github.com>
wrote:

> In
> oryx-ml-oryx-serving/src/main/java/com/cloudera/oryx/ml/serving/als/RecommendToMany.java:
>
> > @@ -72,9 +72,8 @@
> >      for (PathSegment pathSegment : pathSegmentsList) {
> >        String userID = pathSegment.getPath();
> >        float[] userFeatureVector = alsServingModel.getUserVector(userID);
> > -      if (userFeatureVector != null) {
> > -        userFeaturesList.add(VectorMath.toDoubles(userFeatureVector));
> > -      }
> > +      checkExists(userFeatureVector != null, userID);
> > +      userFeaturesList.add(VectorMath.toDoubles(userFeatureVector));
> >        if (!considerKnownItems) {
> >          ObjectSet<String> knownItems = alsServingModel.getKnownItems(userID);
> >          if (knownItems != null && !knownItems.isEmpty()) {
>
> Would it make sense to have checkExists(knownItems != null, userID) here ?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/OryxProject/oryx/pull/51/files#r17687984>.
>