Uploaded image for project: 'Edgent'
  1. Edgent
  2. EDGENT-120

bad graph generation with certain API / oplet sequence

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • None
    • None
    • Console, Runtime
    • None

    Description

      In the graph for TopologyTestBasic, a counter oplet appears to be a source (i.e. there's no other oplet pointing to the counter oplet). This looks odd to me - is this expected?

      Note this source uses a complex tuple type, i.e. a tuple is a Java object.

      The oplets 130, 77, 76 look odd - is this graph starting at oplet 130 expected?
      130 is a counter oplet that looks like a source.
      77 is a fanoutĀ¬ (see View all oplet properties table below).

      There is tag "mcs1".
      See attachment for screen shots.

      //**************************************************************	   
              //Source 2 using complex tuple type
              //**************************************************************
      
              Random r2 = new Random();
              TStream<MyClass1> mc1 = t.poll(
                      () -> new MyClass1(Double.toString(r2.nextGaussian()), 					                                           
                              Double.toString(r2.nextGaussian()),r1.nextGaussian()
                      ),100, TimeUnit.MILLISECONDS).tag("mc1");
      
              mc1.peek(g -> System.out.print(g.toString()));
      
              mc1.modify(tuple -> new MyClass1(tuple.getS1() + "a1 b1 c1 d1 ", tuple.getS2() +" e1 f1 g1 h1 ", tuple.getD1() +1) );
              mc1.peek(tuple -> System.out.println("MyClass1: " + tuple.toString()));
      
              mc1.flatMap(tuple -> Arrays.asList(tuple.toString().split(" ")));
      
              //An asString
      
              TStream<String> mcs1 = mc1.asString().tag("mcs1");
              mcs1.peek(tuple -> System.out.println(" mcs1_source2: " + tuple.toString()));
      
              List<TStream<String>> splits2 = mcs1.split(2, tuple -> {
                  switch (tuple.toString().charAt(0)) {
                  case '-':              //negative numbers
                      return 0;
                  default:               //everything else
                      return 1;
                  }
              });
      
      

      Attachments

        1. CounterAsSourceComplexTupleType.doc
          1.09 MB
          May Wone
        2. CounterSource.doc
          1.09 MB
          May Wone

        Issue Links

          Activity

            People

              dlaboss Dale LaBossiere
              mnwone May Wone
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: