RapidMiner 7.2 to 7.3 sentiment analysis issue

SteveMM

I recently updated my RapidMiner to 7.3, and when I go do a Twitter sentiment analysis I am unable to get any polarity or subjectivity resuults to return.  Is there something different to do in 7.3 than 7.2 for sentiment analysis?  I really need this resolved as I am working on a huge project for work. 

 

Thank you

sgenzer

hi...what are you using for the sentiment analysis?  The Aylien Sentiment extension operator?

sgenzer

I just tested it with the Aylien operator and it all seems to be working fine.

 

<?xml version="1.0" encoding="UTF-8"?><process version="7.3.000">
  <context>
    <input/>
    <output/>
    <macros/>
  </context>
  <operator activated="true" class="process" compatibility="7.3.000" expanded="true" name="Process">
    <process expanded="true">
      <operator activated="true" class="social_media:search_twitter" compatibility="7.3.000" expanded="true" height="68" name="Search Twitter" width="90" x="112" y="34">
        <parameter key="connection" value="Twitter"/>
        <parameter key="query" value="foo"/>
        <parameter key="limit" value="2"/>
      </operator>
      <operator activated="true" class="com.aylien.textapi.rapidminer:aylien_sentiment" compatibility="0.2.000" expanded="true" height="68" name="Analyze Sentiment" width="90" x="246" y="34">
        <parameter key="connection" value="Aylien"/>
        <parameter key="input_attribute" value="Text"/>
      </operator>
      <connect from_op="Search Twitter" from_port="output" to_op="Analyze Sentiment" to_port="Example Set"/>
      <connect from_op="Analyze Sentiment" from_port="Example Set" to_port="result 1"/>
      <portSpacing port="source_input 1" spacing="0"/>
      <portSpacing port="sink_result 1" spacing="0"/>
      <portSpacing port="sink_result 2" spacing="0"/>
    </process>
  </operator>
</process>

 

Thomas_Ott

If you upgraded to RapidMiner Studio v7.3, make sure to update all your extensions to the latest version. We've made some security enhancements that might cause older extensions to not work right.