Uploaded image for project: 'Blazegraph (by SYSTAP)'
  1. Blazegraph (by SYSTAP)
  2. BLZG-872

ant task to build sesame fails, docs for setting up bigdata for sesame are ancient

    Details

    • Type: Bug
    • Status: Closed - Won't Fix
    • Resolution: Incomplete
    • Affects Version/s: trunk
    • Fix Version/s: None
    • Component/s: Bigdata SAIL
    • Labels:

      Description

      The documentation for many things at BigData is simply outdated. For instance it describes how to setup Sesame 6.3 when bigdata already supports Sesame 6.10 to get conveniences of openrdf workbanch I have tried to use it to setup with Sesame 6.10 but ant task that is described in wiki ( ant install.sesame.server
      ) fails with errors like
      " [javac] /home/antonkulaga/denigma/bigdata/trunk/bigdata-rdf/src/java/com/bigdata/rdf/magic/MagicTupleSerializer.java:184: error: name clash: serializeVal(MagicTuple) in MagicTupleSerializer overrides a method whose erasure is the same as another method, yet neither overrides the other
      "

      P.S. Overall I noticed that you use a lot of outdated libraries and together with ancient documentation it creates a lot of problems. Have you ever considered upgrading to Sesame 2.7.x, droping jdk 1.6 support in favor of jdk 1.7, moving from ant/maven to sbt, moving from svn to git or mecrurial?

        Activity

        Hide
        bryanthompson bryanthompson added a comment -

        Some of these points are best handled on the forums. Overall, if you are seeing the MagicTupleSerializer then you are probably in the trunk. Go to http://www.bigdata.com/blog. Get the release notes for the current release (1.3.0). Go from there.


        - The sesame WAR deployment is a pain and does not support bigdata's MVCC semantics (so queries can block one another rather than being non-blocking). If you use the NSS, queries are non-blocking and the total throughput is much higher.


        - We have an open ticket to upgrade to Sesame 2.7.x. Our main focus over the last 6 months has been QA on the highly available replication cluster. This is now out and we are reviewing our priorities.


        - We are moving to Java 1.7 with our next releases. There are some issues to iron out with Jenkins. We have large commercial clients that have relied on Java 1.6 up through the current release. Java 1.7 was initially very broken. We have been slow to adopt it as a result. However, the G1 collector appears to be working now and we have customers that deploy with it.


        - SVN does fine for us. Not everything needs to be replaced.

        I am going to close out this ticket as non-focused and probably in reference to the trunk. I see that another ticket was opened. I'll take a look at that one too.

        Bryan

        Show
        bryanthompson bryanthompson added a comment - Some of these points are best handled on the forums. Overall, if you are seeing the MagicTupleSerializer then you are probably in the trunk. Go to http://www.bigdata.com/blog . Get the release notes for the current release (1.3.0). Go from there. - The sesame WAR deployment is a pain and does not support bigdata's MVCC semantics (so queries can block one another rather than being non-blocking). If you use the NSS, queries are non-blocking and the total throughput is much higher. - We have an open ticket to upgrade to Sesame 2.7.x. Our main focus over the last 6 months has been QA on the highly available replication cluster. This is now out and we are reviewing our priorities. - We are moving to Java 1.7 with our next releases. There are some issues to iron out with Jenkins. We have large commercial clients that have relied on Java 1.6 up through the current release. Java 1.7 was initially very broken. We have been slow to adopt it as a result. However, the G1 collector appears to be working now and we have customers that deploy with it. - SVN does fine for us. Not everything needs to be replaced. I am going to close out this ticket as non-focused and probably in reference to the trunk. I see that another ticket was opened. I'll take a look at that one too. Bryan
        Hide
        antonkulaga antonkulaga added a comment -

        It is great that you are moving to sesame 2.7.x as most of Sesame wrappers (like BananaRdf for instance) use Sesame 2.7.x and bigdata dependency from old Sesame 2.6 creates a lot of inconveniences for developers.

        >
        - SVN does fine for us. Not everything needs to be replaced.

        Well, moving to git/github may greatly increase contributions from people outside of your team as it often does for many libraries who already did such transition. Github+GIT (as well as other modern services and distributed VCSes) provide much more convenient (and more intuitive) way to make pull requests, follow your projects of interest and add issues then sourceforge+svn

        >The sesame WAR deployment is a pain and does not support bigdata's MVCC semantics (so queries can block one another rather than being non-blocking). If you use the NSS)

        Thank you for the warning. I use sesame WAR mostly as webui for managing the database (tasks like writing requests and adding data from turtle file), features that NSS does not seem to have now. In the same time it is not hard for me to code play2 app that will do the same as Sesame Workbench does (but with better UI) and connect to NSS.

        Show
        antonkulaga antonkulaga added a comment - It is great that you are moving to sesame 2.7.x as most of Sesame wrappers (like BananaRdf for instance) use Sesame 2.7.x and bigdata dependency from old Sesame 2.6 creates a lot of inconveniences for developers. > - SVN does fine for us. Not everything needs to be replaced. Well, moving to git/github may greatly increase contributions from people outside of your team as it often does for many libraries who already did such transition. Github+GIT (as well as other modern services and distributed VCSes) provide much more convenient (and more intuitive) way to make pull requests, follow your projects of interest and add issues then sourceforge+svn >The sesame WAR deployment is a pain and does not support bigdata's MVCC semantics (so queries can block one another rather than being non-blocking). If you use the NSS) Thank you for the warning. I use sesame WAR mostly as webui for managing the database (tasks like writing requests and adding data from turtle file), features that NSS does not seem to have now. In the same time it is not hard for me to code play2 app that will do the same as Sesame Workbench does (but with better UI) and connect to NSS.
        Hide
        antonkulaga antonkulaga added a comment -

        > features that NSS does not seem to have now.

        I have to correct myself. I meant "uploading turtle files with webinterface to NSS".

        Show
        antonkulaga antonkulaga added a comment - > features that NSS does not seem to have now. I have to correct myself. I meant "uploading turtle files with webinterface to NSS".

          People

          • Assignee:
            mikepersonick mikepersonick
            Reporter:
            antonkulaga antonkulaga
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: