New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

aidr-tagger-api looking for non-existent userID column in document_nominal_label #15

Open
ajgbangug opened this Issue Sep 25, 2014 · 4 comments

Comments

Projects
None yet
2 participants
@ajgbangug

ajgbangug commented Sep 25, 2014

I run into this exception whenever I check the Human tagged items. Please see exception below.

Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown column 'dnl.userID' in 'on clause'
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
        at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
        at com.mysql.jdbc.Util.getInstance(Util.java:386)
        at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1052)
        at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3597)
        at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3529)
        at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1990)
        at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2151)
        at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2625)
        at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2119)
        at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:2281)
        at com.sun.gjc.spi.jdbc40.PreparedStatementWrapper40.executeQuery(PreparedStatementWrapper40.java:642)
        at org.hibernate.engine.jdbc.internal.ResultSetReturnImpl.extract(ResultSetReturnImpl.java:80)
        ... 129 more
@koushiksinha

This comment has been minimized.

Show comment
Hide comment
@koushiksinha

koushiksinha Sep 25, 2014

Collaborator

Hi AJ,

Can you pull the latest tagger-api code? For some reason, the JSON internal
parser stopped automatic ignoring of unknown fields. We have fixed this in
the latest code in github.

Regards,
Koushik

On Thu, Sep 25, 2014 at 2:58 PM, AJ Bangug notifications@github.com wrote:

I run into this exception whenever I check the Human tagged items. Please
see exception below.

Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown column 'dnl.userID' in 'on clause'
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
at com.mysql.jdbc.Util.getInstance(Util.java:386)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1052)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3597)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3529)
at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1990)
at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2151)
at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2625)
at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2119)
at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:2281)
at com.sun.gjc.spi.jdbc40.PreparedStatementWrapper40.executeQuery(PreparedStatementWrapper40.java:642)
at org.hibernate.engine.jdbc.internal.ResultSetReturnImpl.extract(ResultSetReturnImpl.java:80)
... 129 more


Reply to this email directly or view it on GitHub
#15.

Collaborator

koushiksinha commented Sep 25, 2014

Hi AJ,

Can you pull the latest tagger-api code? For some reason, the JSON internal
parser stopped automatic ignoring of unknown fields. We have fixed this in
the latest code in github.

Regards,
Koushik

On Thu, Sep 25, 2014 at 2:58 PM, AJ Bangug notifications@github.com wrote:

I run into this exception whenever I check the Human tagged items. Please
see exception below.

Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown column 'dnl.userID' in 'on clause'
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
at com.mysql.jdbc.Util.getInstance(Util.java:386)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1052)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3597)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3529)
at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1990)
at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2151)
at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2625)
at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2119)
at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:2281)
at com.sun.gjc.spi.jdbc40.PreparedStatementWrapper40.executeQuery(PreparedStatementWrapper40.java:642)
at org.hibernate.engine.jdbc.internal.ResultSetReturnImpl.extract(ResultSetReturnImpl.java:80)
... 129 more


Reply to this email directly or view it on GitHub
#15.

@ajgbangug

This comment has been minimized.

Show comment
Hide comment
@ajgbangug

ajgbangug Sep 25, 2014

Ok got it! Is it ok if I just get it straight from master? Or should I use the v1.2.0 tag?

ajgbangug commented Sep 25, 2014

Ok got it! Is it ok if I just get it straight from master? Or should I use the v1.2.0 tag?

@koushiksinha

This comment has been minimized.

Show comment
Hide comment
@koushiksinha

koushiksinha Sep 25, 2014

Collaborator

Master should be fine :).

Regards,
Koushik

On Thu, Sep 25, 2014 at 3:13 PM, AJ Bangug notifications@github.com wrote:

Ok got it! Is it ok if I just get it straight from master? Or should I use
the v1.2.0 tag?


Reply to this email directly or view it on GitHub
#15 (comment).

Collaborator

koushiksinha commented Sep 25, 2014

Master should be fine :).

Regards,
Koushik

On Thu, Sep 25, 2014 at 3:13 PM, AJ Bangug notifications@github.com wrote:

Ok got it! Is it ok if I just get it straight from master? Or should I use
the v1.2.0 tag?


Reply to this email directly or view it on GitHub
#15 (comment).

@ajgbangug

This comment has been minimized.

Show comment
Hide comment
@ajgbangug

ajgbangug Sep 25, 2014

Hi just tried out the latest build from master and we're still experiencing the error :(

ajgbangug commented Sep 25, 2014

Hi just tried out the latest build from master and we're still experiencing the error :(

kushalkantgoyal added a commit that referenced this issue Jul 25, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment